• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Tracking issues for a software with different branches is a bit more demanding because you have to identify the branches one issue affects and possibly separately fix them on each branch. One and the same issue could have different resolutions per branch, i.e. invalid if a broken functionality does not exist anymore. Nevertheless, all branches have to be checked, likely in different time frames.

      Unfortunately JIRA does not support the notion of branches. You have to emulate the behaviour using different schemes like:

      • One issue per version that represents a branch
      • Multiple fix versions for an issue
      • Subtasks for an issue or issue links to ckeck and fix the issue for different versions

      Real branching support could help you check on which branch an issue is done, where it has still to be resolved and so on without adding more and more (perhaps loosely connected) issues to your system or forgetting to fix the issue on some branch (no question/warning when resolving an issue with multiple fix versions).


        Issue Links



              Unassigned Unassigned
              3288496aad10 Mihael Vrbanec
              8 Vote for this issue
              10 Start watching this issue