Story #3057

[Sample pipelines] Example pipelines should have link_name for all of the default inputs (samtools etc)

Added by Tim Pierce almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Sample Pipelines
Target version:
Start date:
06/01/2014
Due date:
% Done:

100%

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

Subtasks

Task #3495: Add link_name to GATK3 pipelineResolvedPeter Amstutz

History

#1 Updated by Tim Pierce almost 6 years ago

  • Assigned To set to Tim Pierce

#2 Updated by Tim Pierce almost 6 years ago

  • Estimated time set to 5.00 h
  • Remaining (hours) set to 5.0

#3 Updated by Tom Clegg almost 6 years ago

  • Subject changed from Example pipeline should have link_name for all of the default inputs (samtools etc) to [Sample pipelines] Example pipelines should have link_name for all of the default inputs (samtools etc)
  • Category set to Sample Pipelines
  • Assigned To deleted (Tim Pierce)
  • Parent task deleted (#2985)
  • Story points set to 1.0

#4 Updated by Tom Clegg almost 6 years ago

  • Tracker changed from Task to Story
  • Estimated time deleted (5.00 h)

#5 Updated by Tim Pierce almost 6 years ago

  • Assigned To set to Tim Pierce

#6 Updated by Peter Amstutz almost 6 years ago

I can't even figure out what link_name even means in this context. The "name" link that associates a collection with a project? Or the (undocumented) "link_name" field used in script parameters? For the first case, there (should) already be name links, so if they are not showing up, that's a Workbench bug.

#7 Updated by Peter Amstutz almost 6 years ago

  • Assigned To changed from Tim Pierce to Peter Amstutz

#8 Updated by Peter Amstutz almost 6 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF