Algorithm:
'type=custom&orderBy=name&expand=screensCount,contextsCount'
Notes:
Hi @Amir Katz (Outseer)thanks for the great article - we use it meanwhile regularly.While I totally agree for the part of the contexts...
Note that in most cases, the context count (CC) is 1 and it actually means that it's the 'global' context (meaning that the CF can be used in any project, any issue type). That does not necessarily mean that the CF is actually used. However, if CC==0, it does mean that the CF is unused.
Note that in most cases, the context count (CC) is 1 and it actually means that it's the 'global' context (meaning that the CF can be used in any project, any issue type).
... we found that having a field not on any screen could be a misleading signal. Sometimes we found admins removed it temporarily from screens but the field is still holding values for at least one issue.We feel some kind of double checking is something useful to do - in order not to delete any data which would be considered still needed.
Regards,Daniel
How can i extract all custom field list with information such as the screens the field is added, workflows that use the field, when is the last date the field is used, number of issues that has the field values etc?
Thanks @Amir Katz (Outseer) - apart from https://community.atlassian.com/t5/Jira-articles/How-to-Find-Unused-Issue-Types-in-Jira-Cloud-Using-REST-API-in/ba-p/1862000 and this one ... do you have other articles and posts similar relating to Jira clean up and unused entity clean ups?
It looks like you're new here. Sign in or register to get started.