Workflow Properties

[VIJAYA KUMAR Buntupalli]

I'd like to create a property where I can assign a the Jira Issue to XYZ user once the workflow is in a certain status. I checked the user-workflow-properties support page (https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/) - but I didn't get what I needed - any further help that someone can share?

[Vronik · Accepted solution]

Hi

Look at this, maybe can help you

https://support.atlassian.com/jira/kb/how-to-automatically-change-the-assignee-when-transitioning-the-workflow/

https://medium.com/@erdemucak/changing-assignee-via-workflow-in-jira-c194b12c3a48

https://appfire.atlassian.net/wiki/spaces/JEP/pages/10945510/Assign+Issue+to+User+in+Custom+Field+post+function

Regards

[VIJAYA KUMAR Buntupalli]

Thank you Vronik

[Shalini Pradhan]

Hello @VIJAYA KUMAR Buntupalli ,

Good day! Welcome to Atlassian Community :)

There are 2 ways to achieve this scenario, when Jira user will be assigned a issue when that issue is transitioned to a certain status.

1. Automation

1. Go to your space -> Space Settings -> Automation

2. Create a new rule with:

   • Trigger: "When: Status changes" -> select the specific status (eg. "In Progress")

   • Action: "Then: Assign the workitem" -> select the user (eg. "XYZ user" ).
     Save and enable the rule

2. Workflow post function

1. Go to space settings -> Workflows -> Edit the workflow

2. Select the transition that leads to your target status

3. Add a Post Function ( Perform actions in new workflow editor )  -> Assign a workitem

4. Choose the user

5. Save the workflow

Thank you

[VIJAYA KUMAR Buntupalli]

Shalini Pradhan, thank you for the tip - instead of the automation approach (as unless I have a premium subscription, the number of automations I create will hit a bottleneck in future ;)), I tried your "2. Workflow post function" recommendation and it worked! Thanks a lot.

However, I have a follow up query on the workflows itself and this time it's related with setting the "Status Properties" - I have a "DONE" status and I wanted to restrict editing to ensure no data changes after work is completed. However, despite setting the vaulue to 'false' for the key, 'jira.issue.editable' - I'm still able to change the status! How can I avoid that?

[VIJAYA KUMAR Buntupalli]

@Shalini Pradhan Any suggestions?

[Thiago Wenceslau -Appfire-]

Hi @VIJAYA KUMAR Buntupalli

I’m Thiago, a support engineer at Appfire.

If you are open to using third-party apps, you can easily handle this with JMWE (Jira Misc Workflow Extensions). A nice bonus is that it doesn’t count against your native Jira Automation limits, making it a great fit for routine workflow tasks like this.

Here is a quick example of how it looks through an Event-based Action:

It’s a very straightforward setup. You can create an automation that triggers precisely when an issue transitions to your chosen status, and have the action automatically reassign the issue to the specific user. If you ever need to get more granular down the road, you can also easily layer in extra conditions or filters.

Please contact our support if you have any other questions about this.

Best regards, Appfire support team.