In an automation, how can I transition a Jira software issue (story) cloned from a JSM issue?

[Phil Bustin]

In the Sandbox:

I'm trying to fulfill a somewhat odd request to populate a newly created column in a sprint board with only issues cloned in an automation from a JSM issue to a Jira software issue.

(An alternative might be to assign a unique priority to the created issue in the clone automation, or create a single selection field and in the clone automation, select a value for it, and sort the sprint board by Priority or by the new field.  I haven't succeeded in sorting the Sprint board by Priority.  When I click the sort arrow, thereby changing Order by Rank ASC to Order by Rank DESC, the To Do column is still sorted by issue key Ascending.)

So back to the new column: I created a new Status in the Jira software workflow used by the created issue cloned from the JSM issue, but I'm struggling to figure out a way to use a branch or other technique in the clone automation to transition the created issue to new new Status, that would populate the new sprint board column.  Can you help with that, please?

It appears I was able just now to use a new automation to accomplish the task.  Please stand by.

[Joe Pitt]

Notifications are sent via the notification scheme. So Jim needs to be on the notification scheme for the closed transition.  If Jim has a JIRA id just put him in the close transition for that type of issue. If he can't see the issue he won't be able to view it, but the email will come through. You may need to create a new notification event.

If he isn't in JIRA you can add an individual email to the notification scheme IF the issue is publicly visible.  

[Yoni Rubin]

Thanks Joe. It seems I don't have the option to filter specific types of tickets in the notification scheme. So, Jim will get notifications for all closed issues, instead of those that were closed and had a specific issue type. Is there a way to narrow the notification parameters? 

[Joe Pitt]

You can create new notification events. If you only use the workflow for that one issue type you can replace the current post function notification event with the new one. Then add Jim and the other users you would normally notify for closing. See: 

https://confluence.atlassian.com/jirakb/configure-a-custom-event-notification-for-a-specific-jira-workflow-transition-or-status-720831525.html