I created a Connect app that defines a custom issue field that is updated programmatically. The list of options is very large so I would like to filter them based on the project key of the issue it's being used on. Is using an issue field template the way to go? If so, how do I create one?
The structure of each option is like this:
{ "id": 1, "value": "d00101", "properties": { "projectKey": "DEV" }, "config": { "scope": { "projects": [], "projects2": [], "global": {} }, "attributes": [] } }
Thank you in advance.
Would it not be better to create multiple contexts so that the select list can have different options by project?
So, don't create the custom field as part of a Connect App and manually create contexts? Can you explain how to do this or provide links?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since the issue field will have hundreds of options and because I'd almost finished the app, I did some more experimenting and found out that limiting the project availability for each option using the config property works fine. https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-rest-api-2-field-fieldKey-option-post
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.