-
Suggestion
-
Resolution: Won't Do
-
Any
-
131
-
59
-
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact us if you have any questions or feedback.
Regards,
Michał Tomasik
Software Engineer, Jira Cloud
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
We would like to add support for the "search for issues based on their history"-feature to our custom fields.
According to https://support.atlassian.com/browse/JSP-121642 this is currently not possible. Currently you only get
History searches do not support the 'xyz' field.
So it would be nice if JIRA would support history based searches for custom fields and developers could add it to their custom fields as well.
- blocks
-
JSWCLOUD-9450 As a user I would like to search for historically flagged issues using JQL
- Closed
- is duplicated by
-
JRACLOUD-34103 Ability to use operator WAS / WAS IN / WAS NOT / WAS NOT IN in custom fields
- Closed
-
JRACLOUD-63292 Allow CHANGED JQL search operator on other fields like "type", and custom fields
- Closed
- is related to
-
JRACLOUD-68745 Improve "Was" JQL operator for values that were set on issue creation e.g assignee
- Closed
-
JRACLOUD-77981 Allow JQL history search for the Urgency field
- Closed
-
JRACLOUD-64955 Allow JQL history search for the Issue Type field
- Gathering Interest
-
JRASERVER-27641 Implement history search aka WAS and CHANGED operators for custom fields
- Gathering Interest