I have a Jira project to track work that occurs over hundreds of retail locations. Originally, our team created a label for each retail location in order to help us sort/filter how many issues were occurring per location. However, since labels are manually created, we ended up with multiple similar labels for the same site and the filters did not work as expected (i.e. labels would be named "Site1" "Site-1" "Site_1" etc.)
As a fix, I created a custom dropdown field with the site names pre-populated in order to create some consistency. This dropdown had 400+ options, but it ensured that the location name was always the same.
In the latest update to Jira, custom field dropdowns can not exceed 55 options. Is there a way I can tag Jira issues with information to uniquely identify a site they belong to without having to go back to labels?
Hello @George Weatherall there are now a few apps for cloud that allow you to have the field options brought from a database table. I would explore that option to see if it's a feasible solution for your scenario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.