Details
-
Suggestion
-
Resolution: Fixed
-
539
-
345
-
Description
Hello Everyone,
We are making an important change to our feature request process for the Issue View.
To enhance our development workflow and improve overall efficiency, we have decided to revise the way we handle feature requests for the Issue View. We will be closing the existing parent issue and converting each open sub-task into its own individual task. This change will allow us to better track and manage the valuable input and feedback we receive from our dedicated user community. This change brings us in line with our standard process for how we manage feature requests for all other Atlassian experiences.
We highly value your feedback and encourage you to continue sharing your ideas and suggestions through these Jira tickets. Your input plays a crucial role in shaping the future of our product, and we remain committed to improving the issue view.
If you have any questions or concerns regarding this transition, please feel free to reach out to our support team via[ creating a support request|https://confluence.atlassian.com/support/create-a-support-request-790796816.html].
Thanks,
Ahmud
Product Manager-Jira Cloud
Hi everyone,
We are currently transitioning all users on the old issue view in Jira Cloud products (Jira Software, Jira Service Desk, Jira Core) to the new issue view. You can read more about the new issue view here.
Thank you to everyone who has provided feedback on the new issue view. Your feedback has been used to identify and prioritise feature requests and enhancements. The tickets on our short term roadmap have been moved to in progress. You can see these tickets in the subtasks below or in a single view here
Thanks
Tha Atlassian Cloud team
As more features move to our roadmap, we'll update the subtasks of this issue to let you know what's changed.
You can also stay up to date and get more info about the new issue view by watching the new Jira issue view page in our documentation.
Note: What is and isn't a distinct feature can be tricky to define, especially in something as involved as the issue view. We'll do our best to capture things as accurately and comprehensively as possible.
Attachments
Issue Links
- blocks
-
JRACLOUD-71338 Missing Epic Name field on new Issue Layout settings
- Closed
- causes
-
JRACLOUD-69567 Unable to delete due date from Jira new issue view
-
- Closed
-
-
JST-606169 Loading...
- is blocked by
-
-
- Closed
-
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
- Closed
-
- Closed
-
- Gathering Interest
- is caused by
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-