Mikael Sandberg Community Champion

Ah, missed that it was Jira and not JSM. Unfortunately in Jira this is not possible unless you use an app from the Marketplace. The form in Jira only works on issue create.

Yes, this can be done without using linked custom fields. One way of doing it is to have an automation that triggers on form submitted, you can then use Forms smart values to access the data and append it to the description. Have a look at this article for more information.

Hi @Rene Chin, Welcome to Atlassian Community! Some more context is needed in order to help you. Where are you trying to access your projects? From within Jira/JSM or from the portal? 

Hi @Olesia Zhukova Welcome to Atlassian Community! The error you get in the audit log indicate that the due date field is not on the screen used by the work item. Automations can only change fields that are on the screen.

Your only option would be to only allow a request type to belong to a single portal group, there is no other way around it. And if you need the same request type in multiple groups then you would have to create duplicate request types. By doing it this way you could use a component/label to indicate which "portal group"…

As mentioned, the portal groups are just for organization, nothing else. So the only way you could relate a request type to a group would be if you only allow a request type to belong to a single portal group. In that case you would know which group the ticket is from, but once you allow a request type to belong to more…

Unfortunately that is not possible in JSM, the sharable link that you can create can only be accessed by users that have a Jira/JSM license, it cannot be made public like the one in Jira.

Hi @Katie Lee, Welcome to Atlassian Community! Is the form in a Jira project or in a JSM project? In JSM the form is attached to a request type and users can see it via the portal. For Jira you can now create public forms that you can share with users that do not have access to Jira which was announced here. 

Portal groups are not associated with the request, so you cannot use it as part of your automation unless you only assign a request type to a single group. 

Hi @Hergenhan, Maria, Welcome to Atlassian Community! You can change the customer notification by going to Project settings > Notifications > Customer notifications. In this case it is the Public comment added one that you would want to change. 

Hi @rescuemeco, Welcome to Atlassian Community! Deleting a repository is permanent, and the only way to recover is if you have a copy of the repository locally. 

Hi @Christina Y Walker, Welcome to Atlassian Community! You cannot revert back to the old UI, this change is permanent. This is from the email that Atlassian sent out to all org admins before the change: The new navigation will be 100% enforced for all sites across Jira, Jira Product Discovery, Jira Service Management,…

Hi @Chelsea Lydon, Welcome to Atlassian Community! If you change the "Number of approvers" to Everyone the request will stay in the approval status until everyone has approved. The other option is to use multiple statuses as @Akhand Pratap Singh referred to.

One thing that you could consider is contacting one of Atlassian's partners, most of them have services that can help you with administration. Check out https://www.atlassian.com/partners for a list of partners that could help you. In the past I have worked with Adaptavist for services like this.

Take a look at this article for more information.

There isn't a smart value for the form name, but {{forms.last}} will get you the form template Id associated with the form that was last submitted. Depending on how many forms you have you could then have a lookup table that contains the form template id an the name of the form. To know what the form template id is for a…

Hi @Phillip K Dunn, Welcome to Atlassian Community! It can be done by setting view permissions on the top level pages, view restrictions are inherited down. But this also means that the page you want to give the user edit permissions to has to be on the top level, if it is further down in the page tree they have to have…

Hi @Smin, Welcome to Atlassian Community! You can do this with a status that only allows automations to transition to it and then use an automation to do the transition if the change is outside of the deadline. You also have a second automation that transitions out of the status if the change is updated with a date that is…

The only role in Assets that do not require a JSM license is the Object Viewer role, but that only allows them to view the objects outside of Assets in a custom field that is added to Jira. In order to be able to access Assets you need to have JSM access, as described in this KB.

@Dhanapal Mohanasamy This is awesome start. I for one would like export/import functionality, that would really help us keeping our sandbox environment in sync with our production environment, today we have to manually copy each automation over which is both time consuming and can be error prune.

Hi @Donelson, Terrence (Synchrony, consultant), Welcome to Atlassian Community! Have a look at this KB that describes what you need to do in order to import work items via a CSV file. 

@Markus Hovikoski The API has changed since 2020, you now have to use Get project role for project in order to get the members.

It's been awhile since I used Jira DC, but as far as I am aware @ mention someone does not automatically add them as watchers. The thinking behind that is that it is up to the user to decide if they should watch the work item or not. You could have an automation that automatically add someone as watchers when they are…

Hi @durso, Welcome to Atlassian Community! The only way to stop/reset the SLA is to do one if the actions listed under Conditions. It cannot be done via the API, since that could override the conditions in the SLA. So in your case what I would consider is to add a new status when the team adds an internal comment that…

@Ahmud Auleear I tend to agree with the opinion that moving the Status field to under the Summary will only complicate finding it. The screenshot you included is from a work item in Jira, but if you look at a work item in JSM the space under the summary field does not have the grouped apps button, instead it shows them as…

Is the project you are using a team-managed project or company-managed project? The KB you found only applies to company-managed projects. Once the custom field (user picker or group picker) has been created you need to add it to the request type. Once that is done you can associate it with the approval process in the…

One thing to check is if the user have access to the project, notifications will check permissions so if a user do not have access to the project they will not get notified even if they are mentioned/added as watchers.

Hi @Amali Seneviratne, Welcome to Atlassian Community! Currently only team-managed projects have approvals similar to JSM. You can work around it, I wrote an article about how I did it for a project that needed it, check out Approval process without using the workflow approvals.

Atlassian released a fix for this about a month ago, you can now set the Default comment behavior. Just go to Settings > Product > JSM Configuration and you will see it as one of the first options.

If you go to Global automation you have the option to export your rules to a JSON file that you could then use to extract the names. Currently this is the only option until there is an official API for automations.