![]() ![]() Atlassian uses to help determine which features are popular or urgent enough to be added to our roadmap, so it's possible that we can address customer-requested functionality suggestions for future releases. We invite you to vote and comment on these issues as well as watch them so that you are notified when they are updated. There may be addons on the Atlassian Marketplace such as Teams for Jira Service Management that might extend further options to grouping customers in this way. For example, different SLA's for Organization A - Critical priority issue vs an SLA for Organization A - Moderate priority issue. Using Jira Query Language you can build these SLA's to be as complex or as simple as you need. You can build SLA's that query against membership in an organization. You can use these organizations for any customer grouping you like (employee of a client group, member of an internal department.). Jira Service Management allows you to group customers into organizations. Configuration Guide Works for Jira Service Management Cloud and Server. They can also view all the requests they've raised, via the Request button in the top-right corner of the screen. From here, customers can raise requests in any of the portals they have access to. Thank you again for all your continuous feedback and I will do my best to make progress updates as we go along.You want to define SLAs for each customer separately. The help center shows all of the customer portals in your Jira Service Management instance. 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. ![]() Xray Client ID - please see instructions below. It also fundamentally changes the way our product works so we want to ensure we get it right. Configure your Test Modeller workspace for JIRA X-Ray Watch the video below to learn how to configure. 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. |