Hi guys,
Thanks for your feedback. I have been blessed to have been put in charge of the roadmaps for both the JIRA Cloud ecosystem/APIs and our roadmap for project configuration in JIRA Cloud.
We are actively working on major changes to project configuration – issue types, workflows, screens, fields, permissions, etc. This is cited by users as the biggest source of complexity in JIRA.
Introducing new public APIs for many of the schemes would hinder our ability to make improvements and lock us into the existing project configuration model, which we know to be too complex for most users to understand. Certainly, the reason why an add-on wants these APIs to begin with is to make changes to configuration automatically so you don’t have to rely on users to do it.
We are planning to introduce a new simpler API-driven model for project configuration that will support both a new UI and a more straightforward REST API. We will absolutely share more details as soon as possible – we are trying to unravel some of the oldest, most intricate code in JIRA.
At a higher level, we recognize that there are some types of plugins that were quite common in P2 that we either can’t or won’t build APIs to support as add-ons with Atlassian Connect in JIRA. We are working on both clarifying our roadmap and investments for JIRA Cloud for add-on developers over the next year and how we will communicate them. We will certainly share updates on the developer community site here, and if you’re coming to AtlasCamp in Barcelona, I’ll be speaking on these topics as well.
Cheers,
Dave Meyer
Senior Product Manager, JIRA