Skip to end of banner
Go to start of banner

JIRA Tasks for PS

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Version History

« Previous Version 5 Current »

This document describes how JIRA tasks are setup for PS and how to use/create tasks.

Move JIRA Task to new 'Fix Version/s' if Git Branch Exists

Add label to a JIRA task if 'Fix Version/s' changes during its implementation phase. That is, if a Git branch has been already created for a JIRA task. This may happen because of delays or release date decisions. Once a decision has been made that this feature will not go into the originally targeted V3.3.0 release a new target must be set. To 'move' the JIRA task to its new target (e.g. 'Develop'), change the 'Fix version/s' to the targeted branch. Because of the already existing Git branch, the branch needs to be re-based. The 'move' of the JIRA task and re-base in Git will happen independently. Until the re-base is done, add a label of the following format 'GitBranch_' + branch version to the JIRA task. In this example GitBranch_CoreV3.3.0. Remove the label, once the Git branch is consistent with the 'Fix Version/s' branch.

Re-basing is usually done by the developer who is assigned to this task.

  1. Add label 'GitBranch_' + branch version (current 'Fix Version/s')
  2. Change JIRA task's 'Fix Version/s' to new target
  3. Re-base Git branch to new target
  4. Remove label