RELATED IDEAS
Jira Integration of custom calculated field
We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release name" was suggested by your support team, but that field cannot be integrated with Jira.
We are now using an in-house custom built process to support our needs.
Bastian, sorry I never checked the comments on this so I am sure you solved it a long time ago.
We had programmers run a job that downloads the information we needed from aha, combine it and upload it to Jira. I hate the solution but aha still has not provided the ability to integrate calculated fields so we're still stuck with that solution.
We have the same issue too. In Jira, our solution was to use Premium, where we can make use of the 'Team' field. The lack of integration with this field is frustrating. I think we're going to have to find a workaround too, which is frustrating to say the least.
we have the EXACT same use case as the OP. It is critical for our eng. teams to be able to disambiguate release versions sent to JIRA by doing exactly what Russell proposed.
Besides this specific use case, there are many other uses for us wanting to send calculated fields to integrated systems via integrations. @Russel - would love to find out what your in-house solution did.