Hello!
Is there any update for this? I signed for the EAP but didn’t receive any answer yet.
Thanks.
Hello.
Are there any updates concerning this change and the EAP?
Thanks in advance!
After getting access to this EAP, it seems the field subtask isn’t retrieved anymore for team managed projects. And I don’t see how the user can add this field.
This means we don’t have a direct way to get the child issues of tasks?
Hi @QuentinAlexanko ,
Yes, there is a new API that can be used to manage associations:
At the moment, it only supports team-managed projects, but later we will work on adding support for company-managed projects as well.
Thanks a lot for details!
Even though those fields are likely to be always associated with every project, it would be safer if you could explicitly request them, e.g.: ?fields=project,issuetype,status
Hey @PauloAlves ,
Apologies for the delay, is this problem still relevant? And if so, could you please provide a bit more details about the API call you are making.
You can send those details to mbogdanov@atlassian.com
Hello Mikhail Bogdanov,
We managed to fetch the subtasks using another REST call. It wasn’t needed in the past and it will turn on logic a bit slower (because subtasks aren’t retrieved together with the other issue fields), but there is a workaround for it.
Thanks.
@MikhailBogdanov
Sorry for the delayed reply.
The recent changes have significantly impacted our plugin. Our plugin relies heavily on custom fields and is designed to work with both company-managed and team-managed projects.
If we are now required to manually add custom fields to all issue types across all projects, it will cause considerable inconvenience for our users.
Do you have any suggestions on how we can ensure that the plugin continues to function properly for team-managed projects in this scenario?
Hi @DuHashimoto
Apologies for the delayed reply.
If we are now required to manually add custom fields to all issue types across all projects, it will cause considerable inconvenience for our users.
Do you have any suggestions on how we can ensure that the plugin continues to function properly for team-managed projects in this scenario?
At the moment, the only available solution is to manually associate fields with each TMP project that uses your app. This can be done either by a user through the UI, or programmatically via the REST API. We recognize this isn’t ideal - it’s a step back to when apps needed to be manually enabled for every TMP project, and we know that adds friction.
The good news is that we’re actively working on a major overhaul of field associations, as outlined in RFC-103: Jira Field Configuration Overhaul: Admin Experience and API Changes. While we can’t commit to specific solutions just yet, improving how apps manage field associations is one of the goals of this work.