Florian Bonniec Community Champion

In that case you need to add a post function that set Resolution value to Empty in any transition that go out of Done status. For anything that go in Done status you should set the Resolution to whatever you want.

So as long as you have Portal access for Browse permission, no need for Service Desk Permission in the project for that.

Hi @Yong Xin Choon This table is related to "Atlassian Audit Plugin" app. Do you have it on your JIRA ? It's a system apps so it should be there. Regards

HI @ali.salem This user has probably JIRA Service Desk permission in the project. You should review the permission scheme of the project. Regards

HI @Teke Máté I would use field value condition instead of JQL as it's more performant. In order to be able to reopen a ticket you need to have the transition in the workflow and you should be able to do something similar of what you already have for Resolved. For Reopen I would add a post function that clear the…

HI @Andreas Zweng This video could help you. They are doing rest call to automatically display tracking parcel information from tracking number. It'snot the same but pretty close. Same concept will be needed. Off by 2: Live-coding with Jira Service Management + Forge Regards

You may face this issue. https://confluence.atlassian.com/jirakb/how-to-use-request-type-in-automation-rules-when-language-support-is-enabled-for-a-jira-service-management-portal-1345624050.html Regards

I think so it should be the same object as generic event. Regards

HI @[deleted] Does the automation failed or works. What the rule audit say ? Regards

You do not use Generic Event, but create a custom even and configure your transition to use the new event. 

HI @Alex You could create a custom event, trigger this event in the transition instead of generic event, and configure a Listener on this event. Regards

Hi @Rolf Lader Is it a Custom Scripted field or another Script field type ? I would probably avoid using a scripted field and use a custom field to store the information. You can use listener or automation to populate it. The script field is calculated when you view the issue. If you use a JQL to find it it may be slow…

HI @serge calderara What is the API response when it does not work? Regards

Hi @Yi Liang I do not see how to do it with JIRA without app. It should work with Scriptrunner using dateCompare dateCompare(Subquery, date comparison expression) https://docs.adaptavist.com/sr4jc/latest/features/scriptrunner-enhanced-search/jql-functions Regards 

If it's multiple project you could add both to the automation scope and add a condition at the beginning of the automation to make sure it do not trigger on the second project. I do not think there is any way to do it in the json. Because it's not directly store in the payload. Regards

You have to create a token for this purpose with an account that have org admin permission. Manage an organization with the admin APIs | Atlassian Support Regards

HI @Sumit Rajendra Athani 401 is permission error. The token/account you use do not have enough permission. Regards

Hi @marek.uschanov Have you try to change the preference in your profile ? Profile > Preferences > Autowatch > Disabled. You could also add a branch after your issue create action. Branch on Most Recently created issue then Action Manage watcher and check Remove all existing watchers. Regards

You may need to add OR issueFunction in issuesInEpics("issueFunction in portfolioChildrenOf(\"status = 'to do'\") ")

Do you manage to find the field issueFunction in the custom field list ? It should be listed and tag as locked. No one should be able to delete it but in some past experiences admins removed it from the database directly. The second JQL is correct.

Hi @Robert Nadon I'm using this query from Scriptrunner on my side. Portfolio Regards

Hi @Lisbon Cruz I've not use JSM for a while, and if I recall the transition are on top of the Request Participant section by default. This one may be a custom panel created by an app such as Scriptrunner. You have to look for Fragment and need to be JIRA Admin to list them. Regards

Hi @Arsen Sukias Your second part cannot work as For Linked Issues reference the Version released not the Task and you cannot have a branch action in a branch action. You could create a second automation that add a comment to the parent when a Task is closed. Assuming your Tasks are all closed by this Release automation.…

Hi @Subash.Gurung Based on the Suggestion/Bug tracker, this feature seems to be released for Agent https://jira.atlassian.com/browse/JSDCLOUD-7937 But for Portal there is an open ticket so it's not implemented. https://jira.atlassian.com/browse/JSDCLOUD-13227 Regards

Hi @Juliette Bramall You can use multiple smart value in your automation. {{comment.author.displayName}} - {{comment.created}} {{comment.body}} Regards

You need to be JIRA Administrator in order to create multiple project automation. https://support.atlassian.com/cloud-automation/docs/permissions-required-for-jira-cloud-automation-rules/ Regards

Hi @Arsen Sukias You could use Automation for JIRA that is now included in JIRA Data Center in order to, when a version is released 'button Release from the baord', transition all tasks to close. If you are still using the server version and cannot purchase Autoamtion anymore, you could have a look to Scriptrunner and use…

Hi @juliana.gobbo Yes you can, the automation will have to be listening on version created, then as action, you can create other versions. Rule will have to scope the 3 projects. Projects has to be company managed project. Regards

Hi @Michael Phan , you could have a look to automation for JIRA, but also the REST API. https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-project-versions/#api-rest-api-2-version-post Regards

And you have a transition available from the first status of your workflow to the target status ? If you go on CISD-40, you have as user a transition to do it manually ? If it's not available, automation should not be able to reach the status either. Regards