Marc -Devoteam- Community Champion

Hi @Waseem Haddad Is the SLA re-index process completed on the project? If you makes changes to an SLA the project starts to re-index this change directly, so it can occur that you will have to wait some time before the change is visible on the existing issues.

Hi @Jovita Moguleviciute Welcome to the community. No this is not possible and there is no work around for this. There is a feature request open at Atlassian relating this topic. The feature request is to have more email address set to a single JSM project so multiple requests can be issued via email, it also incorporates…

Hi @Louis Worsch Welcome to the community. Jira Cloud is internet based, so it seems the printer has issues using data from the browser to print. Does this happen with other browser content, if so then I would convey your message to the printer manufacturer.

Hi @Gurpreet Sekhon This is the Atlassian Community, not Atlassian Support. They can be reached via -> https://support.atlaissan.com/contanct/# Are you using the same field configuration scheme, with the field configuration where the account field is set as required on all projects?

Hi @Ieva Zdanaviciute Welcome to the community. If I remember it correctly, I think the syntax needs to be as follows; {livesearch:spaceKey=DOC|size=large|placeholder=Search this space} I think this it the documentation around it: insert-the-livesearch-macro 

Hi @Ravi Chaganti SSO is something a part from new JSM Customer role. All about this new role is explained here: https://community.atlassian.com/t5/Jira-Service-Management-articles/A-dedicated-product-access-role-for-internal-customers-in-Jira/ba-p/2279244 The new JSM Customer role introduce a way to restrict portals…

Hi @Tyler Kosaski No this can't be changed in the field. How does the numbering relate to the Xray test setup you are using?

Hi @Maximilian Mata Your instance makes use of the following app; Translation for Jira Service Management Searched for in on the web. So to add other languages in the selector, the settings in this app need to be changed

Hi @Maximilian Mata Welcome to the community. This option is a marketplace app, as on an ootb instance I'm not able to use or even see this option. What app is used to provide this option. As the option in you 1st screen shot are ootb language options in a company managed JSM project, but is certainly not related to the…

Hi @Ben Robson Welcome to the community. If I go over the options there currently are there is no option for import. https://support.atlassian.com/confluence-cloud/docs/create-and-edit-databases/ You are able to use it in the current closed beta. I suggest you provide this as feedback.

Hi @Gwenaël Durand I have the same behaviour here. I would urge you to raise a bug at Atlassian Support on this en mention the option given in the API don't functon.

Hi @Stiltsoft support Thanks for answering, I was already suspecting it to be table and charts option.

Hi @Nags Subramanian what marketplace app are you using and what is your configuration on the page and the chart look like?

Hi @Adam Taylor You can get this information per project but not overall.

Hi @GG I think you shoild make you call as follows: http://…../rest/insight/1.0/iql/objects?iql= ObjectType = “printers” &page=2

Hi @Horan Welcome to the community. This is not possible. See this issue open at Atlassian; JSDCLOUD-12907 

Hi @Kristen You need to be a Jira Admin or have to been granted the project administration permission or role. If you don't have the project settings option in the menu on the left side on the project you are not able to grant people access to the project. You need to reach out to a Jira or Site admin to grant the user…

Hi @Belén Tarruella This is expected behaviour. You are logged on to the application as JSM agent and you are the responder to the issue. This is the way all ITSM related applications work ootb. You could create a general user that all agents log on with and then that is the responder, but this is bad practice. It also…

Hi @Julian Governale I think so that you have to do it that way, as I don't think assets information is available in that way to the API. So you would indeed need a new CF user (multiple) to add the values to and then you the api cal to read out that field.

Hi @Elizabeth Styles The Disabled messages indicates that the user is still with Atlassian Admin and set disabled there. To re-enable deactivated user follow the steps outlined here But is you are able to access this location in Atlassian Admin, you would need to enable the user first, before you can add the user to any…

Hi @Paul Prata No you can't, as this is auto calculated based on the conditions in the SLA, this value changes on the time the SLA is going to breach.

Hi @Sarah Casner Welcome to the community. Can you clarify a bit more. Is the user referring to the portal, this is most likely; https://<your-instance>.atlassian.net/servicedesk Or are they seeing multiple JSM titles on the portal, are both portals available as open. See Customer Permissions on how portals can be limited…

Hi @Reinhard Mayr No you can't ootb. You can look at marketplace theming apps, like Refined it they are able to do this. There are also marketplace apps from the vendor Deviniti that can extend the information visible

Hi @Somnath Raveenthiran JQL to use is: <Your SLA> operator (=, or other) breached() and status = <Your status>

Hi @Abhinash Thati Welcome to the community. This is most likely related to the fact that on the edit screen, related to the issue type in Jira the priority field is not on the screen. Or a second option could be that is prohibited by the workflow.

Hi @Julian Governale I think currently you have to use the following syntax, {"update":{"[Approver customfield]":[{"add":{"accountId":"[User Account ID"}}]}} I won't know if this would work in relation with assets (as I don't use it), but is the assets is containing the account id. this could work.

Hi @Arun Unnikrishnan Like this. I wasn't aware this is possible,

Hi @Yassin Farboussi You would need to create a new custom field as indicated by @Arensa Prasta Remove the current field from the screens that use it and replace it with the newly created field. In Jira it is not possible to change the way an existing field acts.

Hi @Sakthivelrajan S S Most likely, what happened is that you are not have access to the Confluence space anymore or you permissions on the space have been changed. or you site is accessible anonymously and you can still view information, but you don't have a Confluence license anymore. Reach out to your Confluence admin…

Hi @Vasudha.bhakri Macro's from different 3rd party developers most likely won't work together as that is not why the developer build them, but from their perspective to add extra functionality to the Confluence product You could reach out to both developers and see if there are options to integrate, but that would give…