-
Bug
-
Resolution: Timed out
-
Low
-
4
-
Severity 3 - Minor
-
Issue Summary
When an issue/story is created in the roadmap, we are being presented with a set required fields dialog box, to confirm the issue creation, even though all required fields shown in the box are set (with default value or not).
Steps to Reproduce
- Create a plan in Advanced Roadmaps
- Set a required field at the project
- Add the field as a custom field to use in the plan
You can even set a default value for the field - Create an issue/story in the map
- Click at Review changes
- Click to Save selected changes in Jira
Expected Results
The issue would be created without confirmation, having in mind that all the required fields are set.
Actual Results
The pop-up to set required fields appears and the user needs to confirm all issues' creation.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is duplicated by
-
JRACLOUD-87634 Required Priority field prompts an issue create screen in Plans
- Closed
- relates to
-
JPO-19217 Loading...
[JRACLOUD-92442] While creating an issue in a Plan, set required fields dialog box being presented when all fields are set
This error is impacting the use of the feature.
Please, increase the priority.
A problem that makes a resource unusable should have its priority increased, since there is no alternative path or a workaround as a solution, needing to "waste time" because of a problem, time that could be used in other tasks and not making a repetitive effort.
Please this problem needs more attention.
This is a real shame.
Our organization just bought Jira Premium to use Advanced Roadmaps.
It used to work just fine, but with this problem, a simple and common thing like create issues, turns into a hassel and tedious clicking process.
Please, review the priority.
This is not a LOW priority. It's not only cosmetic.
This makes the feature completely not useable when you have 50 tickets that will be created through the Advanced Roadmap. Please consider changing the priority.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team