Ahmud Auleear Atlassian Team

Hi everyone, Thanks for taking the time to share your feedback here. We're actively fixing bugs as they come in and monitoring everything you post. We'd love to go deeper and hear from you directly. If you can spare 30 minutes, it would genuinely help us shape what comes next. Book a time that suits you here: Zoom link…

@Todd Thomas Thanks for the feedback. We will address the bug and assess the Activity tab buttons. 

Hey Everyone, The beta toggle rollout is now underway and is being enabled progressively across customers. We’re currently targeting completion of the rollout by August 12. We’ll share another update once the rollout is complete. Thanks, Ahmud 

Thanks everyone, this is exactly the kind of detailed, specific feedback that helps us build the right thing. Really appreciate you taking the time, and great to see so much of it building on each other. A few of you have called out similar themes, so I’ll group them: Linked items default to “Add existing”: Yes, that’s the…

Hi everyone, I’m a PM on the Jira Cloud team, and we’re looking into improving the command palette functionality. We know the current experience is inconsistent, and we want to fix it. I’m hosting 30-minute feedback sessions to discuss: Gaps: Actions that still require a mouse. Pain points: What’s slowing your workflow…

Hi everyone, I’m a Product Manager on the Jira Cloud team currently looking into our keyboard shortcut experience. Based on recent feedback, we recognize that keyboard shortcut coverage is inconsistent across Jira and often feels secondary to mouse-based navigation. We are working to improve this and want to ensure the…

Feel free to post any comments or feedback here as well.

Hi everyone, Thank you all for taking the time to share such thoughtful, passionate, and detailed feedback. I hear the concerns, the frustrations, and the fatigue many of you are feeling. I fully understand how even small UI changes can have a ripple effect, especially when they impact documentation, onboarding, or…

Hey Everyone, Thank you again for all your thoughtful feedback. I want to acknowledge the significant concerns many of you have raised. I understand that this change is impacting existing workflows, and I appreciate how disruptive that can be. We made the decision to remove the plain text renderer because it has not been…

Hi everyone, Thanks for all the feedback. Unfortunately, we're unable to offer rollbacks for this update. This change is part of a broader effort to align Jira’s issue hierarchy across all experiences and improve long-term data consistency and feature compatibility. That said, we absolutely want to help you adapt as…

Hey Everyone, Thank you all for your thoughtful feedback and for sharing such a wide range of use cases, concerns, and questions around this change. I fully understand the legitimate concerns raised about the WYSIWYG editor particularly around integration with external systems, the need for reliable plain text storage,…

Hey Everyone, Thanks for the questions. Q: Does this affect paragraph fields only or also short (single-line) text fields? A: The change primarily targets multi-line text fields (like Description or custom paragraph fields), but some short text fields may be affected if they previously used the default renderer. We will…

Hey, We’re beginning to roll out this change starting today, and expect to have it fully deployed by the end of the month. Thanks, Ahmud 

Hey @Tomislav, Yep, that's right. With the changes we're rolling out, sub-tasks will only be allowed one level down from a standard parent issue. That means you won’t be able to create sub-tasks under Deliverables, Initiatives, or Themes either.This is in line with the goal of enforcing a clean, logical hierarchy:Parent →…

Hey @Tomislav Tobijas In Jira, we are moving towards the direction that you can create child issues only one level down from a parent issue. For example this could look like:​ Epics: The highest level, representing large bodies of work.​ Standard Issue Types (e.g., Stories, Tasks, Bugs): These are the immediate children of…

Hey @Rina Nir Thank you for sharing your use case and feedback! I’m a product manager for the Issue View and have the "none" values on my radar. I’d love to connect and discuss further. If you’re open to a call, please feel free to schedule a time that works for you through my Calendly link. Looking forward to hearing from…

Hey Everyone, Thanks for the feedback and all the great questions! I'll try to address them all below: Will the functionality of this feature be extended? We currently don't have plans to extend the functionality of this feature. However, all the requests made via this post will be reviewed and prioritized against other…

Hi Everyone, Thank you for sharing your feedback on the recent UI changes. I understand that these updates have impacted your workflows, and I genuinely appreciate your candid responses and suggestions. The decision to adjust the quick add on menu stemmed from two main considerations. First, feedback from many users…

@Peter Workflow Properties can be used to manage who can link issues to an epic, allowing users to view but not link issues. These properties are associated with specific statuses in your workflow, so you will need to apply the appropriate properties to each status. For example, by using the jira.permission.link.denied…

Hey @vasileios.ntelopoulos I am a product manager on Jira Issue View. I'm looking at hidden when empty behaviour for the issue view and would love to chat about your use case. If you are able to book a time in my calender for a quick 30 min session that would be great. Thanks, Ahmud 

Hi Everyone, Thanks for pointing out the bug about how the button overlays the code. We have shipped a fix to this issue. You should see this fix in your instance now. @Rilwan Ahmed I'll make sure the DC team is aware of this feature but currently, there are no plans to introduce this feature to DC. Thanks, Ahmud 

Hey Maria, The max is determined by the text length of the field names (255 characters). However, it sounds like there is another element that might be contributing to your situation. There is an edge case that if you pin a field and then that field is deleted by an admin, it will still contribute to your max character…

Hi @Lina Maria Castro Ramirez The app is My Reminders which is found on Atlassian's Marketplace. Just to note this app might still appear in the glance view till the end of March. Thanks, Ahmud PM-Jira Issue View

Hi @Jacques Thanks for your comment. I can understand your frustration. We currently working on the solution to referencing an attachment on an issue. We have completed the user testing for this feature and will provide an update closer to the release date. Thanks for your understanding, Ahmud