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

Add the ability to directly create child issues

XMLWordPrintable

    • 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.

      Perhaps this is more of a Portfolio suggestion, but as an Agile Product Owner, I would like to have the ability to add issues directly to Initiatives or other issue types defined as having child issues. This should operate similar to the way Epics operate today, with a + link that adds issues directly to the current epic.

            [JSWCLOUD-17573] Add the ability to directly create child issues

            Karen Aiken added a comment -

            Think this is being fixed by JSWCLOUD-19005

            Karen Aiken added a comment - Think this is being fixed by JSWCLOUD-19005

            Bharani S added a comment -

            This has to be reopened as the "Child Issues" that lists all the issue with the same Parent Link. this will make the users have the option of the seeing both.

            Bharani S added a comment - This has to be reopened as the "Child Issues" that lists all the issue with the same Parent Link. this will make the users have the option of the seeing both.

            Will Peacock added a comment -

            Please re-open this issue.
            Our team would really like this to be in Cloud.

            Will Peacock added a comment - Please re-open this issue. Our team would really like this to be in Cloud.

            Theresa Simon added a comment -

            Please reopen, it is not only needed for server but also for cloud!

            Theresa Simon added a comment - Please reopen, it is not only needed for server but also for cloud!

            Eleni Wagner-Oikonomi added a comment -

            why is this closed? We need in our company!!!!!!!!

            Eleni Wagner-Oikonomi added a comment - why is this closed? We need in our company!!!!!!!!

            Line Lengfelder added a comment -

            We need this one reopened. It's kind of peculiar that epics have their "add a child issue" button as default, but whith Premium and issue type hierarchy the possibility for the same function on higher level issue types is nowhere to be seen. 

            Please reconsider.

            Line Lengfelder added a comment - We need this one reopened. It's kind of peculiar that epics have their "add a child issue" button as default, but whith Premium and issue type hierarchy the possibility for the same function on higher level issue types is nowhere to be seen.  Please reconsider.

            Italo Lobato added a comment -

            Atlassian Support mentioned there is a similar open request for this feature https://jira.atlassian.com/browse/JSWCLOUD-19005 

            Italo Lobato added a comment - Atlassian Support mentioned there is a similar open request for this feature https://jira.atlassian.com/browse/JSWCLOUD-19005  

            Italo Lobato added a comment -

            +1

            I've raised a ticket CES-25837 requesting to reopen this request

            Italo Lobato added a comment - +1 I've raised a ticket CES-25837 requesting to reopen this request

            CEDRIC DEVAUX added a comment -

            Hello,

             

            What is the update of this feature?

            CEDRIC DEVAUX added a comment - Hello,   What is the update of this feature?

            Jerome Drew added a comment -

            Please re-open this issue and complete this feature.

            Without this feature, there is no way for developers to see a logical hierarchy of issues within the issue itself. The hierarchy edit feature is then only useful to PMs and leadership, but there's no way for developers and other users to open a parent ticket and see all of the child issues of a parent. Linking is fine, but really there needs to be a way to create or at least view child issues.

            The data is already there. At very least, a read-only field "Child Issues" that just lists every issue with the same Parent Link would help users see and click on a child issue of a parent.

             

            Thank you!

            Jerome Drew added a comment - Please re-open this issue and complete this feature. Without this feature, there is no way for developers to see a logical hierarchy of issues within the issue itself. The hierarchy edit feature is then only useful to PMs and leadership, but there's no way for developers and other users to open a parent ticket and see all of the child issues of a parent. Linking is fine, but really there needs to be a way to create or at least view child issues. The data is already there. At very least, a read-only field "Child Issues" that just lists every issue with the same Parent Link would help users see and click on a child issue of a parent.   Thank you!

            Pau Pineda added a comment -

            I would love to see this feature implemented!

            Pau Pineda added a comment - I would love to see this feature implemented!

            Guillaume LAURENT added a comment - - edited

            hello,

            even if plan view is very usefull, it's a shame that it's not possible to create child tickets from new Parent ticket (same as it is possible to do with Epic ticket)

            Guillaume LAURENT added a comment - - edited hello, even if plan view is very usefull, it's a shame that it's not possible to create child tickets from new Parent ticket (same as it is possible to do with Epic ticket)

            Jesse Gray added a comment -

            With the replacement of `epic` for `parent` this is yet another example of the job half done and people painfully making work-arounds for their users.   

            DO THE WHOLE JOB. 

            Jesse Gray added a comment - With the replacement of `epic` for `parent` this is yet another example of the job half done and people painfully making work-arounds for their users.    DO THE WHOLE JOB.  

            Karen Aiken added a comment -

            Is there a way to reopen this request?

            There's a community discussion with some activity interest:

            https://community.atlassian.com/t5/Jira-Software-questions/Can-I-add-quot-Add-Child-quot-button-to-a-Issue-type-in-a-non/qaq-p/2096308?utm_campaign=&utm_content=post&utm_medium=email&utm_source=atlcomm#U2237830

            Karen Aiken added a comment - Is there a way to reopen this request? There's a community discussion with some activity interest: https://community.atlassian.com/t5/Jira-Software-questions/Can-I-add-quot-Add-Child-quot-button-to-a-Issue-type-in-a-non/qaq-p/2096308?utm_campaign=&utm_content=post&utm_medium=email&utm_source=atlcomm#U2237830

            Matthew Hunter added a comment -
            Atlassian Update - June 1, 2021

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - June 1, 2021 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              62b5633ca848 Robert Jahrling
              Votes:
              2 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: