Marc -Devoteam- Community Champion

HI @Mubashra Naeem If you removed if from a screen and added it back to the screen, no data will be lost. Removing a field from a screen, will not remove the data set in the field from the system. This doesn't even fall in the 1st or 2nd scenario

Hi @Lloyd Stoltz Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request. This will help other community member trying to solve the same or provide them with a work around P.S. If the answer is very valuable to you, please share some kudos.

Hi @Omkar Rajale Create a new custom field of type Labels. This is not an option on a custom field of type dingle select, users can't add options to such a field. Or revert yourself to see if there are possible options on the Atlassian Marketplace.

Hi @Mubashra Naeem Did you delete this custom field and retrieved it from trash, or was it completely gone and you recreated it? If it's the 2nd then all data is also gone and can't be retrieved.

Hi @cjmorris Welcome to the community. To integrate Sailpoint with Atlassian Cloud, see https://documentation.sailpoint.com/connectors/atlassian/cloud/help/integrating_atlassian_cloud/introduction.html You can't directly connect to a single Atlassian Cloud application 

Hi @sravani vennapusa There is no Free subscription for Align. Even on using a paid version you need to contact Atlassian Sales for an Align subscription.

Hi @Spirit Super I you have automation in your DC you could create read only text fields and set these fields on the view screen. Then on the transition have the automation rule copy the values from the fields that need to be read only to then newly created fields. Make sure that the original fields are not on the Edit and…

Hi @Sebastian Brinkmann @Walter Buggenhout has a valid solution ,but if you want to do this with the automation. Then in the email body, set it like this. {{#lookupIssues}} {{key}} | {{summary}} {{/}} Also see this KB Article as example, automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next 

Hi @Dan Langenberg Are you editing the correct workflow, make sue that its the workflow related to the work type

Hi @Nadav Loutati Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request. This will help other community member trying to solve the same or provide them with a work around P.S. If the answer is very valuable to you, please share some kudos.

Hi @Sara Innes To use the Due Date on the Request Type, when filling the from from the backend the field needs to be on the request form. This has no relation with the Schedule issue permission. this is due to the fact the users in the role Service Desk Customer never had the option to schedule issues, this is only for…

Hi @Vidya Subramanya Please explain your requirements on the thread here. Otherwise if you are in need to look at development done you can reach out to an Atlassian Partner in you region. https://partnerdirectory.atlassian.com/ 

Hi @Leonellys Ramírez Look at the configuration of the JSM project, or if you can't, get a Jira administrator involved. Does the user where the API is created with have a JSM license does this user have the correct permissions. I suggest to reach out to manage engine, for further support

Hi @Nadav Loutati No there is no field that provides this information. Also the automation you mention, fire on a schedule an create an issue, there is not information in an automation rule on issue completed, as the automation rule is not completing this. On work items many automations can run, there is a section called…

Hi @Leonellys Ramírez Does the project in JSM use the work item/issue type Incident? But I think it's probably related do to the fact there is no permission management in JSM free, you will need a paid subscription for this. I think you will need a paid subscription for this. But I think it's best to relate this question…

HI @Wolff Sébastien Can you show your complete automation rule and a related asset object, where this attribute is set. Try this. After the lookup, set a log action that shows the found object and the Utilisateur attribute information {{lookupObjects.Utilisateur}. Then you can create this also to create the variable.

HI @Vidya Subramanya Please provide more context, what do you want from a dashboard? If you simply want to create a dashboard, see documentation. what-is-a-jira-dashboard 

Hi @Witold Zabdyr For cloud there is no SpacePermissionManager class for direct use in Confluence Cloud, For Confluence Cloud, use the Confluence REST APIs, which allows the creation and modification of users, groups, and their roles within spaces. 

Hi @Jamie Stanczyk This is probably due to the fact that a sandbox always receives any new features straight away, as it is always on the "Continuous" release track. Check the Release Track option in Atlassian Administration of your instance. Is this set to "Continuous" or "Bundled" If not, this feature could be rolling…

Hi @Ayyanar R Welcome to the community. Here in community, most of us are Atlassian users like yourself and we don't have access to your environment. This community is an open public form. Atlassian Support can be reached via https://support.atlassian.com/contact/ Please provide more context, on the raised issue, are there…

Hi @Sara Innes Can tyou provide screenshots and the related error in the screen shot?

Hi @Rob Peters Yes in the history it will show, as via the portal you can't raise an anonymous ticket Yes you should be able to do this. * Edit the Confluence page where you want to place the widget. * Insert the HTML Macro by typing /HTML in the editor. * Paste the JSM widget code into the HTML macro. * Save and publish…

Hi @Praveen Galagali Welcome to the community. Based on the API documentation, you are missing some required information , like; * page title * page id Also see this community article, Make-a-table-on-a-Confluence-page-via-the-Rest-API 

Hi @Gsfyris You can use markup. See the options here , https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all 

Hi @Marco Wettstein Welcome to the community. To me this seems like a bug, as conditions can't be checked if the work item/issue doesn't exist yet. And indeed this is a BUG, its already. marked as a bug, AUTO-2007 

Hi @Sara Innes Welcome to the community. No changes are made on this topic in Jira SM to my knowledge. Is the field due date still on the create screen of the issue the users want to create?

Hi @Rob Peters The field raise this request on behalf of is only visible for jira admins and jira project admins on a JSM project, if granted a JSM license Or is there a custom field with this name placed on the form and marked as required? But even if a user can access the portal anonymous, the reporter will be set with…

Hi @Sudarshan Singh Welcome to the community. Are you on Cloud or DC and what API endpoint are you using? Does the call you are making result in a successful execution (http 200)?

Hi @Nadav Loutati Welcome to the community. Create a filter, that finds the issues created by these automations and show the columns required, like assignee and resolved. As an extra you can create a dashboard in Jira and use the filter results gadget to show this information, then you won't have to select and open the…

Hi @liam_johnson Welcome to the community. Do you have the correct permissions on the project on the View development Tools permission and do you have the correct permissions in in GitHub, GitLab. GitHub integration: https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/