customfield_15000 does not have any context associated and I want to display all dropdowns present for the same custom field but as I do not have context id I am not able to use below rest api.
GET /rest/api/3/customField/{fieldId}/context/{contextId}/option
and when tried to get the custom fields options using below link I am getting 405 as method not allowed
/rest/api/latest/customFieldOption?fieldId=customfield_15000
If you rename an issue type, the change will propagate to all existing issues of that type. Some filters explicitly mentioning that type would be broken, as well as gadgets fed by them. Anyway, broken filters could be fixed by typing the new issuetype name.
Lea,
I doubt you can rename an issue type. Why not create a new one and then bulk move the tickets to the new issue type?
Here's documentation on how to go about it
https://confluence.atlassian.com/jiracoreserver073/moving-an-issue-861257345.html
Victor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Ignacio! Very helpful.
Thanks Victor - yes, I can rename an issue type, but will need to make sure that my filters are reset as Ignacio stated above.
Really appreciate all the help and guidance. Thank you both.
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.