What is the challenge? |
Sometimes a custom field type needs to change to meet evolving reporting needs. |
|---|---|
What is the impact? |
In the current config a resource would need to create a new custom field and populate values to the new field. Which can take time and introduces human error (even if bulk updating). |
Describe your idea |
I'd like the ability to convert a Predefined Choice List which is a single-select field to a Predefined Tag Field (multi-select). The movement in this direction makes sense bcs a user would have only populated 1 value. Converting (rather than creating new and populating) would remove the human error. New values can be added after the conversion. |
Oh yeah wanted to add that I wouldn't have to go back and adjust any Aha <> Jira Integrations. Now the above should popup a message saying "this field is linked to an integration and may need config adjustment on jira side".