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.

[sudhakar]

HI

We can  get list of stories that are associated with other stories in the form of links using JQL Search Extensions plugin 

JQl : (linkType in( "is blocked by") AND linkedIssueType = Story ) will give you list of stories that are linked with other stories in the form of blocked

https://jqlsearchextensions.atlassian.net/wiki/spaces/SEARCH/pages/3375124/JQL+Reference+Cloud#JQLReference(Cloud)-LinkedIssueType

 Regards,

Sudhakar