Custom fields for issues plus auto-assigning and searching custom fields
Related to: #28431 (closed)
User interviews highlighted that users want the ability to auto-assign specific fields as an issue is created, especially if the issue is raised through a third party ticketing system. Accompanied by the ability to search/query these custom fields.
A use case is:
A developer sets up a custom field in GitLab for a 'support request number'.
A customer raises a ticket into a third party ticketing system.
The developer pulls that ticket from the third party ticketing system into GitLab issues, so he can action the customer's request.
The 'support request number' field is automatically populated with the information pulled from the third party ticketing system.
Team Lead wants to know the progress of the issue.
Team Lead knows the 'support request number' so he searches for it within GitLab which returns the issue the developer is working on.
I guess a workaround for this is using labels / API? However, I guess you could end up with an issue which has a vast number of labels and certain types of information, i.e numbers as opposed to words, are not as well suited to a label.