Is it possible to have an issue which is blocked by a number of other issues not be allowed on a sprint or as a higher ranking in the backlog?
Further clairfication from my comment below...
I'm thinking of the "blocks" link not status. If issue A is blocking issue B then I would like to be alerted if B is ranked a higher priority in the backlog or if B is added to a sprint without A.
Depends on how you identify your issues as Blocked. If you use a status of "Blocked", then in the Agile Board don't map the Blocked status to a column or exclude Blocked status from your Board Filter. Then the issue won't show in the Backlog. Once the status is changed, it will be displayed on the Planning Board.
Same question here on recent JIRA 7.3.1
The default link relation "blocked by" (or "blocks" from the other Point of view) is used. It should not be possible to add an issue A to the sprint (or to rank it higher than) as there are one or more issues B,...,N that block issue A.
Even adding a listener/trigger/event for this seems not easily configurable?
Any hints or comments appreciated.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs