Hi, it would be really great to extend Plans API to be able to modify/update "Views".
Also I would love to be able to get via API all issues, that are "Removed from Plan" (keys + possibly "Removal date"), so we could work with Automation to delete them completely or set a Security Level via automation to hide them completely in Jira for normal users (so they get removed for example also from Jira Dashboard views, and not only in Plans).

THANKS!

Hi abalaba@atlassian.com  - one more question please.

The Plans API does not provide/allow for the views of a plan.
That is if a modification of the 'Basic view' was done in UI, or is needed to be done programmatically, API does not get/put that. Not that I found how.

Am I missing something in the API? Should plan views' configuration part of the plan setup?

Thanks

Hi abalaba@atlassian.com , 

Certainly. 
We want to be able to add placeholder cross-project releases to a plan, programmatically.
These should not yet be associated to specific project releases.

When we add them, we want to verify first that the names of the plans do not exist yet to avoid suplicates.

As the Get Plan API doesn't return cross-project releases which are not associated with project releases that is a bit difficult at the moment, programatically.

Thanks 

Hi 9c653040c2de,

Thanks for your feedback.

On the cross project releases topic, would you please share a little more on your use case?

Thanks & Regards,

Arkady Balaba

Hi,
a0c6d525c56b and abalaba@atlassian.com 
Thank you for the shiny new API, it's a great improvement.

I've noticed however that the Get Plan API returns an empty array in crossProjectReleases if those exist but are not set with releaseIds yet.
It will return an array with only cross-releases project which are set with project releases if those exist.
You can add "empty" cross-project releases in UI and in the new API - which is great for planning.
In UI you can see them, and they should also be returned by the Get Plan API in the response json.

Also, in the documentation for the Update plan, please include that it must use header "Content-Type: application/json-patch+json".

Thanks again for these APIs, you published them in the nick of time for me
Great work.

Thank you!

Hey 7d9ae0d87192 ,

The fix was merged and the listing endpoints should include a "legacy" plans too.

Regards,

Arkady Balaba

Hi Arkady,

Yes, it does work for new plans. Please update the ticket once it also works for "legacy" plans. Not sure how to distinguish new from legacy plans.

Thanks!

Hey 7d9ae0d87192 ,

This might be because of the legacy plans are not included (the fix is on the way). How old the plans you trying to retrieve are? Could you try to create a new Plan and test it with the APIs? 

As for the Connect scopes, all of our resources require Jira admin access. We will update the docs portal with the info.

Regards,

Arkady Balaba

Hi Arkady,

Thanks for sharing the new resources.

It says "Connect apps cannot access this REST resource." in the documentation, however, it can be accessed but the list of plans returned is empty:

{
  "maxResults": 50,
  "total": 0,
  "isLast": true,
  "values": []
}

Could you please update the Connect scopes required or is it not supposed to be accessible from Connect? Also, why is the list of plans returned empty, even though we do have plans on this Jira instance?

Hey everyone, 

This is to note, we have just released the very first version of Plans APIs. There are currently two resources supported - Plans and Plan teams.

Please find the respective documentation on our APIs portal:

• For Plans - https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-plans/#api-group-plans
• For Plan Teams - https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-teams-in-plan/#api-group-teams-in-plan

Regards,

Arkady Balaba