-
Suggestion
-
Resolution: Timed out
-
1
-
9
-
Problem Statement:
When using the advanced search in Jira, fields that should be restricted to Team-managed projects are being available to be chosen. This causes some issues especially when they have the same name as global fields.
Suggested Solution:
Team-managed fields should be restricted and visible only across team-managed projects. It should only be visible if the filter is applied to a team-managed project to where this field belongs to.
Why this is important
Making team-managed fields visible across the instance isn't a good user experience as:
- Team Managed projects are simple and all its settings should be kept inside it
- In case a field from a TM project has the same name as a global one, it'd be hard to identify which one the search is referring to.
- is related to
-
JRACLOUD-85929 Search needed for all custom fields across TMP and CMPs
- Gathering Interest
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management