nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Global issue collecting status of atomic issues

Piotr Czabanski

In complex products taking parts many developers and applications. To better understanding my question J will give the exmaple as a story. Let's take Product Manager and one issue given by client. Product is indeed bunch of servers and application taking care about mass information delivery by email, voice, sms and fax. Client want to see radio signal strenght of the gsm gateways - let's name this issue - Global Issue. Well, this single simple issue mean for developers, one issue for Interface Web Designer, secound for Core System to change interface with SMS Server and the thrid for SMS Server to gather this information form GSM gateways. So Global Issue cover 3 issues - let's call it Child Issues. Transformation Global Issue into Child Issues can not be done by product manager, his knowlage is too weak - it can be done by other developers after consider the Global Issue. Other side - it is not important for our product manager, he wants to know what's going on with his Global Issue. So how to do that? Is it possible to have Issue showing the total predicted and spent time of all child issues. Is it possible to present in Global Issue the worst resolution and status taken form childs issues? How to solve this by Jira? PM working on higher level of abstraction and our current Jira implementation is not satify in this case.

Accepted answers

Renjith Pillai

Probably you should look at structure plugin https://marketplace.atlassian.com/34717

All comments

Rahul Aich [Nagra]

Looking at your problem, I would recommend that developers add sub-tasks to the parent task.

Sub-task issues are useful for splitting up a parent issue into a number of tasks which can be assigned and tracked separately. Splitting issues into smaller tasks often provides a better picture of the progress on the issue, and allows each person involved in resolving the issue to better understand what part of the process they are responsible for.

All the sub-tasks related to a parent issue are summarised on the parent issue's main screen (see 'Working with Sub-Tasks' below). Sub-tasks always belong to the same project as their parent issue.

Sub-tasks have all the same fields as standard issues, e.g. Summary, Description, Reporter, Assignee, Status. Note that sub-tasks have a different set of issue types from the standard issue types.

Have a look at this link on creating sub-tasks

https://confluence.atlassian.com/display/JIRA/Creating+a+Sub-Task

Rahul

Piotr Czabanski

Well - Product Managers works on many "virutal products" being composed form "real products", so your proposition is near be perfect except one point - subtask have to belong to the same project. If would be possibilites to create links to the subtask as the issue in other project...... is it possible?

Renjith Pillai

Probably you should look at structure plugin https://marketplace.atlassian.com/34717