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

Create more ergonomic order of Operations

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 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.

      As the number of available issue-operations keeps increasing, keeping the interface simple is a great challenge. Actually the order of operations is not very user-friendly, as many commonly used operations tend to be right in the middle, and the least-used operations are found right at the beginning.

      I would propose changing the order of operations.

      Here is the order, i would suggest:

      • Edit issue
      • Comment Issue
      • Attach File
      • Screenshot
      • Assign (to me)
      • Link Issue
      • Create Sub-Task (Please set the link on the word "Sub-Task" instead of "Create", then its quicker to find for the common user)
      • Vote Issue
      • Watch Issue
      • Log Work
      • Clone Issue
      • Move Issue

        1. operations.jpg
          29 kB
          Gerd Gueldenast

            [JRASERVER-5344] Create more ergonomic order of Operations

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3051016 ] New: JAC Suggestion Workflow 3 [ 3677262 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2612849 ] New: JAC Suggestion Workflow [ 3051016 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2574835 ] New: Confluence Workflow - Public Facing v4 [ 2612849 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2355382 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2574835 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2122719 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2355382 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2084453 ] New: JIRA Bug Workflow w Kanban v6 [ 2122719 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 875149 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2084453 ]
            Oswaldo Hernandez (Inactive) made changes -
            Component/s Original: Web interface [ 10126 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 718057 ] New: JIRA Bug Workflow w Kanban v6 [ 875149 ]
            Roy Krishna (Inactive) made changes -
            Backlog Order (Obsolete) Original: 30220000000
            Bugmaster Rank (Obsolete) Original: 51090000000
            JIRA Support Rank (Obsolete) Original: 58330000000
            Studio Rank (Obsolete) Original: 53580000000
            Support Rank (Obsolete) Original: 53580000000
            Workflow Original: PM Feature Request Workflow [ 225640 ] New: JIRA PM Feature Request Workflow v2 [ 718057 ]
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Priority Original: Critical [ 2 ]

              Unassigned Unassigned
              bb13e57032de Gerd Gueldenast
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: