Hi 684cb16ed833. Do you happen to have any update on the timeline for implementing this functionality? You mentioned that it was probably "months" out back in December; wondering if there is a month that you're now targeting.

59886a7e4545 - Completely understand 'your take' on this ticket and why you feel it should have been raised as a bug.

and yes - also completely understand your frustration with the length of time it takes for some items to be resolved (I have a list of documented long-term items which we have run up against both as users and administrators -  which I have previously passed onto Atlassian for their consumption). I too wish Atlassian would 'sort out' some of the more basic/grating issues for their user base before adding new bells and whistles, but like you I have very little influence on their decision-making processes.

Again - frustrating, but we have to wait unfortunately. 

Kind Regards - Steve

steve.davis1 The fact that it's filed as a Suggestions doesn't mean it's not a bug  

The settings of a context require you to give 2 inputs: (1) An issuetype and (2) a project, so one would expect that the context applies to this particular combination of (issuetype,project) while in reality it does not. This is clearly a bug for me.

I totally understand Atlassian has a lot to do, but 20 years for a basic feature? If you ask admins what they would've liked more - Atlassian Intelligence or a few bug fixes - I'm pretty sure I know the answer.

59886a7e4545 - As far as I can see this is a 'suggestion', not a bug ticket.

Whilst I appreciate the sentiment that yes, having to vote for new features and wait is frustrating (believe me, I'm in the same boat - I don't work for Atlassian!) and yes, when it is a bug fix ticket it's even more frustrating - in this instance it's effectively a 'New Feature' request. So the change requested is not 'due to a bug' but due to a limitation of the existing software.

There are obviously hundreds (if not thousands) of tickets in process by Atlassian for all sorts of changes, as well as their own wishlist - so we can only wait until they have appropriate resources available to implement this.

Kind Regards - Steve

Hi 684cb16ed833 

1. It's ridiculous that your customers need to vote on bug fixes in order to get a working software.
2. Am I just missing the "EoM update" which was probably due by end of Dec'24? 

684cb16ed833 53214b82d75d this is a huge pain point for lots of Jira Cloud users. Please ensure that the priority is set accordingly.

Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

Thank you for the update, 684cb16ed833 .

We'll wait with bated breath for the updates ahead. Out of the many feature requests our company has submitted / voted on, this one is easily in the top 3.

Wishing you and the rest of the team happy holidays! 🎄✨🎁

Thanks dcd56a4d94b6 - appreciate the question! Sorry I missed it earlier. It's looking like months rather than weeks at this stage, and we will be rolling it out as part of a broader series of changes to how fields are configured - I'll be back with more updates.

I appreciate the attention this request is getting, 53214b82d75d, f91199aa80c0, and Carol.

Given the dependencies / prerequisites, do you anticipate it taking weeks, months, or years to implement?