Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-44053

Not possible to Change the order of Status buttons in Jira On-Demand

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 1
    • 1
    • 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.

    Description

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

      In Jira we would like to change the order of which Status buttons that appears on the issues (see attached image Status buttons in worng order.png).

      I saw that the <tt>opsbar-sequence</tt> could be the key. The guide below does not work as you are not allowed to enter the <tt>-tags in the property field.
      https://answers.atlassian.com/questions/145963/is-it-possible-to-change-the-order-of-workflow-steps-in-the-issue-view

      When that did not work I found the following guide, but when using the opsbar-sequence with values 100, 200, and so on the Status buttons still comes in wrong order (see image Property config.PNG).
      https://confluence.atlassian.com/display/JIRA/Advanced+Workflow+Configuration#Advancedworkflowconfiguration-customisingtransitionsonviewissue

      How can we change the order of the Status buttons in Jira On-Demand?

      Best Regards
      /Hazze Molin

      ps. Also I still cannot find the current On-Demand version to enter in the Affects Version field when submitting this bug request. ds.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              bb63cb565371 Hazze Molin
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: