Log inSkip to main contentSkip to sidebar
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.
Jira Software
Issue Summary
If you are performing 'Edit issue' action from automation, only first 50 fields will showed up for 'Choose fields to set' option.
Steps to Reproduce
Create an automation which has 'Edit issue' action.
Make sure your site has numerous custom fields in it. Try creating a field which starts with letter R, S, T, U as they comes last in alphabetical order.
Then look for your custom field. The search engine will look for all the fields who has matching string.
If your custom field falls under first 50 fields which search engine look for, you would see the field appearing in 'Choose fields to set' option.
In case your custom field falls after 50, you won't be able to see the field appearing in 'Choose fields to set' option.
I have created custom field S in my test instance and I am not able to see the field appearing in 'Choose fields to set' option.
As shown in below screenshot, only 50 fields will be populated from search result
Expected Results
All the search results should be appearing correctly
Actual Results
Only first 50 custom fields with matching criteria will show up.
Workaround
You can rename the field as per alphabetical order.
Use the "Additional Fields" section to set the value of the field manually through JSON.
This also affects Jira Service Management (JSM) and would be REALLY helpful!
Susan Waldrip
added a comment - This also affects Jira Service Management (JSM) and would be REALLY helpful!
Unassigned
Sayali Alhad
Votes:
3Vote for this issue
Watchers:
7Start watching this issue
Created:
Updated:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
Suggestion
This also affects Jira Service Management (JSM) and would be REALLY helpful!