What is the challenge? |
Bi-directional sync of the Jira team field is only supported for some Aha! custom fields |
|---|---|
What is the impact? |
Mapping to a predefined choice list is not ideal because it requires us to manually update and map each team field, which is unsustainable given the number of teams we have in Jira. |
Describe your idea |
This idea is specifically to add support for editable choice lists - ensuring the Jira Team field can automatically stay in sync with an editable choice list field in Aha!
|
Thanks for the thoughtful suggestion and clear examples. This specific use case, syncing Jira’s Team field with an editable choice list in Aha!, was difficult to support in our initial implementation. The current design prioritizes consistency and data integrity across a wide range of Jira configurations.
We see the value of keeping teams in sync without manual list maintenance, especially at scale. This is something we’re considering for future enhancements, and we’ll continue to monitor customer feedback to help guide our approach.