Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-191

Synchronize JIRA subtasks priorization with GreenHopper ranking

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • 5.6
    • 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.

          [JSWSERVER-191] Synchronize JIRA subtasks priorization with GreenHopper ranking

          Katherine Yabut made changes -
          Workflow Original: JAC Suggestion Workflow [ 3064736 ] New: JAC Suggestion Workflow 3 [ 3663488 ]
          Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
          set-jac-bot made changes -
          Link New: This issue details JSWSERVER-566 [ JSWSERVER-566 ]
          set-jac-bot made changes -
          Link New: This issue details JSWSERVER-567 [ JSWSERVER-567 ]
          Owen made changes -
          Workflow Original: Confluence Workflow - Public Facing v4 [ 2621878 ] New: JAC Suggestion Workflow [ 3064736 ]
          Rachel Lin (Inactive) made changes -
          Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2320907 ] New: Confluence Workflow - Public Facing v4 [ 2621878 ]
          Status Original: Closed [ 6 ] New: Resolved [ 5 ]
          Katherine Yabut made changes -
          Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040173 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2320907 ]
          Katherine Yabut made changes -
          Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2028732 ] New: JIRA PM Feature Request Workflow v2 [ 2040173 ]
          Katherine Yabut made changes -
          Workflow Original: JIRA PM Feature Request Workflow v2 [ 739213 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2028732 ]
          Martin (Inactive) made changes -
          Backlog Order (Obsolete) Original: 1200000000
          Story Points Original: 2
          Workflow Original: GreenHopper Kanban Workflow v2 [ 301906 ] New: JIRA PM Feature Request Workflow v2 [ 739213 ]
          Assignee Original: Nicholas Muldoon [Atlassian] [ nmuldoon ]
          Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
          Priority Original: Major [ 3 ]

          Hi Jean-Christophe,

          I see the previously described cases and agree with argumentation listed there, thanks for that!
          However, my case is somewhat similar to the situation Jesse has described just the reason is different.
          I wish to use JIRA task as the functional work item (specification, user story) and create sub-tasks for the exact technical tasks - JIRA allows it and that's fine. Further we need to assign different sub-tasks to different team members. Each of them has his/her own tasks list that is being prioritized through GreenHopper.
          Unfortunately, I cannot prioritize sub-tasks (wich are the actual technical tasks for each particular person); this obstacle makes me to think of workarounds that make JIRA + GreenHopper usage not so straight-forward I had imagined. My current workaround is to create several tasks (not sub-tasks) - each of them being a particular technical task - and linking them together, which kinda works (I can assign them individually and prioirtize in GH) but this is not as smooth I'd like it to be.
          What can you suggest me?
          Thanks in advance!

          Juris Deduskevics added a comment - Hi Jean-Christophe, I see the previously described cases and agree with argumentation listed there, thanks for that! However, my case is somewhat similar to the situation Jesse has described just the reason is different. I wish to use JIRA task as the functional work item (specification, user story) and create sub-tasks for the exact technical tasks - JIRA allows it and that's fine. Further we need to assign different sub-tasks to different team members. Each of them has his/her own tasks list that is being prioritized through GreenHopper. Unfortunately, I cannot prioritize sub-tasks (wich are the actual technical tasks for each particular person); this obstacle makes me to think of workarounds that make JIRA + GreenHopper usage not so straight-forward I had imagined. My current workaround is to create several tasks (not sub-tasks) - each of them being a particular technical task - and linking them together, which kinda works (I can assign them individually and prioirtize in GH) but this is not as smooth I'd like it to be. What can you suggest me? Thanks in advance!

            Unassigned Unassigned
            jchuet JC
            Votes:
            5 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: