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.