User privileges, such as data and page access, via the REST APIs are identical to privileges in the interface. The user token needs to include "bearer" in front of the user's API Token (API Key).Īuthorization is based on the authenticated user when Jira Align REST APIs are called. These tokens do not expire until t he user generates a new token or is deactivated. Authenticationīearer authentication using API tokens (tokens can be generated on the User Profile page of Jira Align) is supported. Version 1 of Jira Align REST API is still supported, but no additional resources will be added all development is on version 2 of the API. The URIs for resources have the following structure: This documentation is for version 2 of the Jira Align REST API, which is the latest version. For complete documentation on the resources, along with HTTP responses and sample requests, please view the documentation available in your environment at: This page provides an overview of the API and documents the REST resources available in Jira Align. Using the API, you can perform most actions available through the user interface, as well as simplify user management, mass update work objects, and d evelop integrations between Jira Align and other applications. Thank you again for all your continuous feedback and I will do my best to make progress updates as we go along.The Jira Align REST API exposes key objects in Jira Align's people, work, and time hierarchies via a standardized programmatic interface. Both of these aspects are fundamental to how you manage your users and the access control of the system, and we need to take the time to make sure we are doing it in the best possible way possible. Right now we are in the process of bringing in groups into JIRA Service Desk (Ability to add groups to tickets, JQL search for groups etc) and also making enhancements to the group infrastructure (Allowing agents to be managing groups etc).Īgain I want to stress this feature requires big changes to our underlying user management and permission infrastructure. We will do our best to keep everyone updated with the latest development regarding this feature and to share our designs/progress once they become available. As mentioned in my previous comment this is already in active development but there are quite a few number of moving parts to implementing this feature. We understand many of you will need to make business decisions around when this feature is available, however we do not have a meaningful ETA we can share. If you are interested to see how the feature is progressing feel free to leave your details to join one of our upcoming usability test and provide us feedback on the feature itself. It also fundamentally changes the way our product works so we want to ensure we get it right. Unfortunately the development of this feature is taking considerable time as the security model for users in Cloud is very different to Server. We are building it as a core part of the product, so there will not be any additional cost for this capability - and we are building it for both Server and Cloud. If you are on JSD Server you can evaluate these options and choose to purchase them if they meet your needs.Īs mentioned before this feature is one of our highest priorities and the JIRA Service Desk team is actively developing this capability. Collection Issue View for Service Desk and Teams for JIRA Service Desk are both add-ons which aim to provide customer grouping capabilities for JSD Server. We do have a very vibrant marketplace which our expert partners develop add-ons that extend our products.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |