Post-function not working as intended

[Janine Daniels]

Hello all. In my workflow, at the end of the creation step, issues enter status Pending Approval. Since issues need to be approved before being assigned, I have a property for this status that only the allowed group can change the issue fields. To stop people assigning issues to people before they have been approved, I added a post function to this transition, to assign all issues to myself. However, when a user selects "Assign to Me" when creating an issue, somehow they are able to bypass this, and the issue is not reassigned to me after creation.

I even tried changing the rule to "Clear Field: Assignee", but this does not appear to work either. Any suggestions as to whats going on?

[Grigory Salnikov]

Hi!

Does hiding "Assign to me" button works for you?

[Janine Daniels]

I dont believe I have the possibility to do that. That is not a field that is in my list of configurable fields. I would also like users to be able to use that option after the Pending approval step...

[Grigory Salnikov]

I'd suggest you go through different options represented in these 2 questions:

Hide the Button Assign and Assign to me when a specific status is set

Can we remove the 'Assign; button in the View Issue page. in Jira 4.4.5

There're a couple of solutions that I think could work.

[Grigory Salnikov]

I'd also like to forward here this answer by @João Palharini

Hi Robert!

There's also the workflow properties, that are defined in a per-status basis. You can add the following to any status you want:

Property Key: jira.permission.assign.denied
Property Value: <leave blank>

 In order to edit these properties, go to the workflow's "Edit" page, then (on the Text view), click "View Properties" on the right of any status.

--
Cheers!

Joao

[Janine Daniels]

Thanks for your replies :) unfortunately I dont think either of your links in your first response can help me - since this is happening during the issue creation, the issue hasnt actually reached a status yet. Therefore, people are able to assign it to themselves before that. As for the permissions - I DO have a permission set at Pending Approval, that only a certain group can change assignees. But users are able to set it BEFORE reaching this status. Users should be able to freely assign to whoever they need to freely after this first status, however.

My current workflow, as I understand it, should allow the user to create an issue and even if they set an assignee, when it transitions through the post functions, it should remove the assignee from the field anyway and assign it to myself. However, the post function does not appear to be doing this right now. Since its happening during the very first step, Create Issue, Im not sure what else to do.

[Grigory Salnikov]

Oh, I see... Yes, you're right.

Let me try something in my environment and get back to you.

[Janine Daniels]

Thank you very much! For your reference, here are both versions of the post function for the create issue step I have tried:

and:

Both times, the issue was still assigned to the original assignee when reaching the following status.

[Grigory Salnikov]

Pew-pew :)

Seems like I've managed to hide the entire section with the help of  CSS.

Put the following code in the announcement banner:

<style type="text/css">
#assignee-container.field-group {
 display: none;
}
</style>

And try to create an issue.

Does this solution suit you?

[Grigory Salnikov]

Oh, I'm sorry, you have a Cloud version... My bad :(

I always forget to pay attention to the product versions.

Not sure if the announcement banner is configurable on Cloud already.

[Grigory Salnikov]

By the way can't you just remove the Assignee field from the issue creation screen?

[Janine Daniels]

So, I didnt initially set up the project myself, and had to do a bit of investigating. I never made a create issue screen for myself, and I see it appears to be using a default one across all operation types. I will attempt to make unique ones for each step and see if that helps. Thanks!

[Grigory Salnikov]

You're welcome! I think it should help.

Should you have any difficulties, please, don't hesitate to go back here!

Good luck!