Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-11020

Issue post function to "rank to bottom" upon status change

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Answered
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      AS A developer using jira having transitioned a ticket from one state in a workflow to the next I WANT the issue to appear at the bottom of the queue SO THAT we can maintain first in first out for each step in the kanban or scrum work board

      AS A system admin I WANT to add a post function to some workflows that will rank an issue to the bottom of the queue when it transitions states SO THAT in a work board (kanban or agile) when issues move out of one state, they queue up at the bottom of the next state by default, rather than current behaviour of apparent 'random' insertion (based on global rank).

      AS A system admin I WANT a global parameter to 'Set rank to bottom upon any state change" SO THAT I can make that the system-wide default behavior

      AS A project admin I WANT a project parameter to 'Set rank to bottom upon any state change" SO THAT I can make that the project-wide default behavior, or override the system-default behavior

      Current behavior of 'random-ish' insertion could almost be considered a bug/defect for Kannan teams..

      version: whatever is on OnDemand at 8/8/2014

      For example, if we have the following linear workflow states:

      • New -> Ready for Specification -> Specification -> Ready for Design -> Design -> Breakdown -> Estimation -> Ready for Development -> Development -> Review -> Resolved -> Documentation -> Closed

      When something moves from 'Ready for Desgin' into 'Desgin', it should be at the bottom of the design queue. When it moves from Estimation to Ready for Development, it should be at the bottom of the Ready for Development queue.

      This is not ALWAYS the desired behavior, especially if one has taken pains to set a global priority, but in some teams focusing on flow this works well.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              f1dc925b931b JamesM
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: