-
Bug
-
Resolution: Fixed
-
Medium
-
18
-
Severity 3 - Minor
-
1
-
Issue Summary
Environment
Jira Cloud
Steps to Reproduce
- Create a screen for creating sub-tasks that includes a required field
- Ensure that the project has multiple sub-task types that all use that screen for creating an issue
- Start creating a new sub-task in the parent issue and select a sub-task type other than the default.
- click create, the create sub-task screen should be shown
Expected Results
The Selected sub-task type from the parent issue would be carried over to the create issue screen.
Actual Results
The selected sub-task type is re-set to whatever the default is in the create issue screen and is not carried over.
Workaround
Currently there is no workaround. If you encounter this issue, don't bother setting the type for projects that you know are impacted. Alternatively you can change the required fields to no longer be required or remove the required fields from the create issue screen for the sub-tasks to prevent the create sub-task screen from blocking the sub task creation.
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- causes
-
PCS-16885 You do not have permission to view this issue
- is resolved by
-
BENTO-3331 Failed to load
- mentioned in
-
Page Failed to load
[JRACLOUD-71728] Creating Sub-Tasks where create Sub-task screen is required does not preserve selected sub-task type
Folks outside my team trying to address things to us have continual problems with this. It is highly disruptive for between-team work. Please fix it soon.
Hi,
This causes confusion, it would be great to have this fixed. Thanks.
This has been an issue for me and a source of lost or miss assigned tasks. Please address this quickly!
I just had another occurrence where the subtask type of a high priority ticket was incorrectly set due to this bug. Please prioritize a fix for this soon as it is a core feature of our day-to-day use.
Is someone from Atlassian still gathering impact on this? It's still impacting our Jira users on a regular basis, across departments. It's extremely frustrating.
I really don't understand how the benefits of doing inline subtask creation was seen as a better experience than the costs of having your subtask-type wiped out after typing your summary. Is inline subtask creation really that much better of an experience over a having subtasks created of the wrong type?
Just posting again that this still occurs regularly for our business. It causes users a lot of frustration and causes the people who triage new issues unnecessary confusion.
Have posted a comment an year back but surprisingly still nothing.. this hampers my teams day-to-day work and time. Sometimes even causes issues in process flow as we practice different workflows for different subtasks. Please have it fixed ASAP.
Please have it fixed ASAP. Surprised that this problem does not have hundreds of votes. Cos it's a day-to-day routine.. which does not work properly .
Thanks
This continues to impact our business, and managers keep having to move issues to the right issue type and have the reporter fill in the information properly since the fields vary per issue type.
Please remove the "issue type selection" if it isn't going to carry through correctly to the Create Subtask screen.
Or please make the Issue Type field blank on the Create Subtask screen so that the user has to select the issue type again.
+1 for fixing this. It's very frustrating.
It's NOT a low priority and is probably a very easy fix, as they already correctly bring across the Summary field into the custom create screen correctly.
I agree - that was really disappointing to see this move to the long-term backlog. This continues to be a pain point for us. It's not a viable option for us to remove required fields from the create screen (or to make them optional).
Is there an expected resolution date on this yet? As a product defect it's disappointing this hasn't been addressed.
Same here - this is causing a lot of confusion for people on our teams.
I agree this is a bug and I hope it is fixed soon. People keep making this same mistake when entering subtasks. The type selection is really important to us. This is really bad user experience.
As this is a BUG and not a feature request, I expect you guys @Jira to pick this on priority. We're working on multiple subtask types each having a different workflow. It definitely affects our process and creates a mess. Hoping you guys would take this up and get back asap.
Thank you so much!!!