+1

Voted and watching. Our site needs this. We have lots of projects where there is a one-to-many project setup. The one project oversees many development projects so the higher hierarchy is in the one project and they want to setup the Epics in the many development projects (directly from the parent project) ready for engineers to split the work required to complete the Epics created.

NB - This does not need to be a pop-up, it could work like linked Issues. Instead of selecting Jira site (local or other ones) in the first dropdown you select project instead.

Hi 810d4b5a4eb3, I was able to find your case, and I also want to share that we identified the cause of this change in behavior in the past week, and are currently tracking it at JRACLOUD-80148: Wont be able to create child issues under Epic if you have workflow validator in create transition. Please add a comment in your support request so it is reopened, and your support engineer will be able to assist you with a fix for your site while the permanent bug fix is deployed.

Rene C, I left a comment here because Support told me to after I reported the issue to them.  If there's a way to privately provide you with the support ticket number, I'll be happy to do so.  I agree, with you that the issue we are experiencing just started happening last week and therefore has something to do with a change that must have been made.

Hi 810d4b5a4eb3, this is a Suggestion/Feature request, and the behavior you describe is different, but also it is not expected, I suggest raising a support request for our team to give it a look, as something may have changed recently, or there might be something specific to your set up.

I'm not sure what was recently done, but my users can no longer add a child issue directly from the Epic when there is a required field in place on the Create workflow step.  Please fix this as it hinders our efficiency.

Greetings - just wanted to check in to see if there's been any new development decisions surrounding this request. This would be a tremendous help to our technical and project management teams to collaborate on 'shared epics' in this manner. Thank you sincerely for your consideration on this! 

Hey @Ahmud Auleear, is there any development around this?

Thank you Ahmud. I've added time this week via your Calendly link. 

Ahmud Auleear - I booked time with you on Wednesday July 12 at 5:30am ET. I will also send you a screenshot regarding this to your email in advance. Thank you! 

We decided to migrate all our epics into the same project as the underlying tasks, so I don't have an input to this issue.

 
Hello,

I am a Product Manager on the Jira Issue View team. 
Thank you for taking the time to share your valuable feedback with us.

Your input is greatly appreciated, and I would like to learn more about your specific use case to better understand your requirements. Could you please book some time with me using this Calendly link? Alternatively, feel free to reach out to me at aauleear@atlassian.com if you prefer.

Thank you again, 

Ahmud 
PM-Jira Cloud

Please look at all the times this has been logged.  I pulled out a few examples I found - I gave up looking and following the trail but this is obviously something people want to see fixed.  Many issues have been closed as duplicates.  (Take all those comments, votes, and watchers, and add them to see how many people are reporting this). 

• JRACLOUD-75660 Create sub-tasks popup screen on New Issue View - Create and track feature requests for Atlassian products.
• JRACLOUD-72380 Provide a way for users to pop open the full Create Sub-task form from the New Issue View - Create and track feature requests for Atlassian products.
• JRACLOUD-75567 Ability to create Epic child in another project directly in New Issue view - Create and track feature requests for Atlassian products.
• JRACLOUD-75648 Cannot create child issue from Epic in new issue view when there is required field - Create and track feature requests for Atlassian products.
• JRACLOUD-76062 Quick create subtask doesn't work on subsequent create with validator - Create and track feature requests for Atlassian products.
• JRACLOUD-76102 In the new issue view, create sub-task does not open dialog box - Create and track feature requests for Atlassian products.
• JRACLOUD-75078 Can not create subtasks from Epic when there is validator on New Issue View. - Create and track feature requests for Atlassian products.
• This issue JRACLOUD-72506 Creating a subtask / issue in Epic should open in a pop-up - Create and track feature requests for Atlassian products.

Our company also relies on the model of Parent projects with Epics and Child projects with Stories and below. There are countless people that complain about the UX due to this limitation. Can someone from Atlassian at the very least comment on why this is a Low priority? 

Can someone from Atlassian let us know if this issue is being tracked as a bug/feature enhancement, etc?  It was created almost 4 years ago, so will this be fixed?
This is logged as a subtask to another issue. 
It is unassigned.
It doesn't show as "Gathering Interest". 
Not sure what other fields are needed to be entered to get visibility, but there's a request by several to raise the priority.
We just want to be sure this isn't being lost in a backlog due to the issuetype or settings. (Other issues have been closed as a duplicate of this subtask, so it is likely the "interest" is much higher than what this even shows).

I will repeat what others have said - this should be a higher priority.  Some of the usability on the Cloud version is more frustrating, such as this.

1) Because this does not open in a pop-up, many of our users are MISSING entering data on the fields.  The only data they enter is the summary line because that is all they see.  It is not intuitive to them to create that summary line, then click into the issue, then update it.  (More work and MUCH is getting missed.  This is causing a lot of data integrity issues and requiring manual cleanup).
2)  Please raise the severity.
3)  Please prioritize this HIGH.  

As for votes, most of my coworkers would likely vote on this if they knew to.  We have had a lot of complaints about this, and it is impacting our day-to-day work productivity.

I seriously hope this gets addressed soon.   It would really improve cross-team / project collaboration. 

Ouch! What an actual deal breaker this is!

We also are limitted to a setup where Epics and Tasks are in separate projects, and now, when migrating from an on-prem Jira to Jira Cloud, it is suddenly no longer possible to create child issues within an Epic.

I'm sorry to say this but it is seriously bad, and you need to increase the priority to "High" on this on.

We literally have no choice to stay on our soon-to-be obsolete on-prem solution for now

Usability is really poor if you create an Issue Type Scheme containing just the issue type of Epic.  Create an Epic and attempt to add a child issue.

No option to select issue type, enter the summary and press the Create button without any user feedback.

This should resolve mandatory fields configured in the workflow (like the built-in Advanced roadmap Team field that cannot be made mandatory in the field configuration)

My question would be how to turn this feature OFF.  We have a project that does just that.  But we found out that when the popup appears, it doesn't link the Story to that Epic which is weird.  We don't know how they did it, but would like that disabled.

The option to open a new issue popup would help us in two ways:

• To be able to select a different project to store the issue in. Sometimes we have a story for another team under our epics.
• To be able to work with required fields upon creating an issue. When we have required fields we cannot create new issues 'inline'. We then get an error icon saying the issue could not be created. Better would be to open the popup so we can set required fields.

This is a serious regression (from our perspective), as we currently put Epics (shared by 25+ Teams) in a dedicated project.  We don't want the PBIs (Story, Bug, etc.) in the same project as the Epics.

Another issue - You can't create issue under the epic if it have required fields on creation (from  workflow validation on field configuration). 

Hello, please mainly add back the possibility to change the project for the new child issue. Thank you!

Thanks for the feedback on creating an issue from an epic and the ability to change the project. I just wanted to provide an update that we will not be working on this ticket in the short term, but will keep it open to monitor the number of votes and to revisit in the future. I have also assigned myself to this ticket. We have a range of requested improvements planned for the new issue view and so have had to prioritise based on impact and votes. Thanks!

Context:

In my master project, product owners of different teams create their epics. However product owners can create story for other teams in their epic. To do so they can follow below steps:

1. In Cloud JIRA, create an epic 

2. From agile board in backlog view, they can "Create issues in epic"

3. When they click on "Create issue in epic" then, "Create issue" window opens

4. In "Create issue" window, on the top they can find a field "Project" to select the project name, where issue has to create.

Problem:

When open epic in issue view, and try to create issues with in epic, then "Project" field doesn't appear. Steps are:

1. Open epic in new tab

2. Click on "Create issue in epic" button

3. Under "Issues in this epic", issuetype dropdown appears, and product owner can add summary. but, product owner can't select project name.