Automatically update due date when an issue move from a sprint to another

[nicolas.rigaill-ext]

Hi everyone, 

I'm looking for an automation to performs  2 actions on issues : 

1. When an issue is moved from the backlog to a sprint, Update both Start date and Due date. --> I have an automation for this one, and it works well

2. When an issue is moved from a sprint to another, Update only the due date (start date must remains in the initial sprint) --> I can't find how to realize this one :( 

I tried something with If/else block, but it doesn't work.

Does anyone have an idea ? 

Thnak you,

Nicolas

[Bastian Stehmann · Accepted solution]

HI @Marzi Goodarzian,

just to get it right.

You want that one group of users can see only one issuetype and another group of users can see only another issue type?

[Marzi Goodarzian]

Hi @Bastian Stehmann

Yes thats right.

[Nic Brough -Adaptavist-]

I would still say issue security is the right way to do this.  Define an issue security level to match each issue type, and then have a post-function on the "create issue" transition that sets it by issue type (have a different workflow per type)

[Bastian Stehmann]

I think this should work using Issue Security.

If you create a Scheme with two security levels, called Bug and Task and for each level, you add the users that should be able to see the Bugs or Task, and assign that scheme to your project, you can use this security levels to restrict the users.

To have that working proberly, you must ensure that the users select the right security level when creating issues.

If you want the security level always set on creating an issue, you can use Script Runner for example to set the security level depending on the issue type.

[Bastian Stehmann]

Ah, you are too fast, @Nic Brough -Adaptavist-

[Marzi Goodarzian]

Is there any way out of this?

Come suppose that user 1 and user2 see issue 1  and user3,4 see issue 2 and...

and this isn't depend on security level that select by user.

[Bastian Stehmann]

You can set the security level as post function and hide the field for editing, then it does not depend on the user and the user can not change it (even without hiding the user will not be able to change it, if the user is only assigned to one security level, because the user can choose only from that levels where the user is assigned to.

[Marzi Goodarzian]

Hi

thanks @Bastian Stehmann

Thanks @Nic Brough -Adaptavist-

[Marzi Goodarzian]

According your help, prolem solved.
thank you

[Marzi Goodarzian]

there is a problam!!

this operations dont work when a usuall user create issue, usuall user is  a person that isn't in any security level. this person when create issue the security level is null! 

[Marzi Goodarzian]

):

[Nic Brough -Adaptavist-]

A user must be included in a security level to be able to use it.

[Marzi Goodarzian]

Hi 

thanks @Nic Brough -Adaptavist-