Project

General

Profile

Actions

action #1658

closed

move does not need a from argument

Added by coolo almost 11 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2014-02-20
Due date:
% Done:

100%

Estimated time:

Description

the from argument in move is actually nonsense - it's easy enough to figure out where the requests are. We might want to offer a --from argument in case we want to move Base:System's request, but only those in E

Actions #1

Updated by aplanas almost 11 years ago

  • Status changed from New to In Progress
  • Assignee set to aplanas
Actions #2

Updated by aplanas almost 11 years ago

  • % Done changed from 0 to 100
Actions #3

Updated by aplanas almost 11 years ago

  • Status changed from In Progress to Resolved
Actions #4

Updated by coolo almost 11 years ago

  • Status changed from Resolved to In Progress

your commit is bogus. The cwd() has no role in this.

The requests should come from whatever staging prj they are in - according to the staging metas.

Actions #5

Updated by coolo almost 11 years ago

On a 3rd thought: without a 2nd argument - the functionality of move can easily be integrated into select. For that the requestFinder class needs to look into metas too

Actions #6

Updated by aplanas almost 11 years ago

  • % Done changed from 100 to 50

I think that I see the problem. Working on it.

Actions #7

Updated by coolo almost 11 years ago

see also 1625 for #5

Actions #8

Updated by aplanas over 10 years ago

  • % Done changed from 50 to 100
Actions #9

Updated by aplanas over 10 years ago

  • Status changed from In Progress to Resolved
Actions #10

Updated by coolo over 10 years ago

  • Target version set to Staging sprint 3
Actions

Also available in: Atom PDF