-
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
[JRACLOUD-77547] Hide Team Managed fields from Advanced Search
Component/s | Original: Jira Issue Search - Frontend [ 53297 ] |
Component/s | New: Issue - Search - Frontend only [ 77950 ] |
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | New: cll-tf2202410 |
Support reference count | Original: 8 | New: 9 |
Link | New: This issue is related to JSWCLOUD-23749 [ JSWCLOUD-23749 ] |
UIS | Original: 2 | New: 1 |
UIS | Original: 0 | New: 2 |
Support reference count | Original: 7 | New: 8 |
Support reference count | Original: 6 | New: 7 |