Bug #3990

[Workbench] "Re-run pipeline" buttons should put the new pipeline-instance in the same project as the original

Added by Sarah Guthrie almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Radhika Chippada
Category:
-
Target version:
Start date:
10/07/2014
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
0.5

Description

It's very difficult to organize the pipeline instance reruns because there is no GUI way to specify which project to rerun a pipeline instance in, there is no (obvious) GUI way to move a pipeline instance once it has started running, and the default is the home project.


Subtasks

Task #4125: Review branch: 3990-owner-when-rerunning-pipelineResolvedRadhika Chippada


Related issues

Has duplicate Arvados - Bug #4037: [Workbench] Re-run a pipeline (using "Re-run same version" or "Re-run latest version") buttons create the new pipeline in Home project.Rejected

Associated revisions

Revision 4146cc48
Added by Radhika Chippada almost 5 years ago

closes #3990
Merge branch '3990-owner-when-rerunning-pipeline'

History

#1 Updated by Tom Clegg almost 5 years ago

  • Subject changed from Re-run with latest and Re-run options do not rerun the pipeline-instance in the same project to [Workbench] "Re-run pipeline" buttons should put the new pipeline-instance in the same project as the original
  • Story points set to 0.5

#2 Updated by Tom Clegg almost 5 years ago

  • Target version set to Arvados Future Sprints

#3 Updated by Radhika Chippada almost 5 years ago

  • Status changed from New to In Progress
  • Assigned To set to Radhika Chippada
  • Target version changed from Arvados Future Sprints to 2014-10-08 sprint

When the current project is writable by the current user, put the new pipeline instance in the current project.

#4 Updated by Brett Smith almost 5 years ago

Just one style/speed comment: instead of saying visit page_with_token(user); visit instance_path, you can just say visit page_with_token(user, instance_path). This will save Capybara a whole round-trip to the server, which seems worthwhile given how much our integration tests are growing.

That's my only nit. This is good to merge, thanks.

#5 Updated by Radhika Chippada almost 5 years ago

  • Status changed from In Progress to Resolved

Applied in changeset arvados|commit:4146cc481cec9847eb41d3e5ba7602b4f33d2096.

Also available in: Atom PDF