Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

write sprint end date in existing custom field

Lars Blaschka
Contributor
May 11, 2020

Hi guys, 

is it possible to automatically write the end date of the current sprint a item is assigned to in a existing custom field in a linked issue?

For example: There is a feature request in our service desk. We create a linked issue of this service desk issue in a project backlog and assign it to the next sprint. As soon as this next sprint starts, we set the end date of this sprint. Now I would like an automation which writes the end date of the started sprint in a custom field "expected release date" in the linked service desk issue. 

Is this possible and if so, how?

We use the add-on "automation for jira".

 

Thanks in advance!

Cheers, Lars

2 answers

0 votes
Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 11, 2020

Hi @Lars Blaschka 

You can access to this value with this :

{{sprint.endDate.format("dd/MM/yyyy")}}
Lars Blaschka
Contributor
May 12, 2020

Hi @Mohamed Benziane , 

I am not quite sure if I do this correct... I just dont know how to set the automation up. 

Right now I have set that if the field "end date" of a linked issue is changed, then the value "expected release date" of the issue in serviceDesk shall be updated by "{{sprint.endDate.format("dd/MM/yyyy")}}" but nothing happens. I think because the field end date is not enabled in my project / issue screen. And I am not sure if the field end date is the same as the end date of the sprint.

It drives me crazy.... Do you have an idea?

 

Cheers, Lars

Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 12, 2020

What is your automation rule ? Can you share is with us ?

Lars Blaschka
Contributor
May 13, 2020

Hi @Mohamed Benziane , sure, here is the automation. I am sure that the mistake is the field "end date". It is not the field I need to add....

What I really need is the field in the second picture. The end date of the active sprint a linked issue is added to. You can see it in the backlog below the name of the current active sprint. Its called sprint end date, but i cannot choose it in the automation...

 

image.pngimage.png

Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2020

Ok i see, for me the easiest way is to create two automation rule :

- one rule that will put the end date of the sprint in each issue of this sprint (you can narrow the list of issue with a condition) in a customfield that you will create (or use one that already exist)

- one rule that will update in the linked issue the field "expected release date" whenever the field (of the rule number 1) is updated.

Let me know if i'm not clear.

Lars Blaschka
Contributor
May 13, 2020

Would this not just split my one automation rule i want to create in two? 

I would also need the name of the field Sprint end date (marked in the second picture above) to create rule number one of your suggestion. 

So this would not realy help me. Or am I wrong?

Cheers, Lars

Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2020

Yes, because if you want to access to the sprint end date (the date in your second screen) you need a sprint trigger in your automation, but with this trigger you can't access to the linked issue (the issue in your service desk)

Lars Blaschka
Contributor
May 13, 2020

Okay, thats an interesting hint.

Do you think the automation could work like this (screen attached)?

image.png

Mohamed Benziane
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2020

i just tried your rule (For "Linked issues") and it doesn't work

sprint.png

0 votes
Jim Edgeton May 11, 2020

Hi @Lars Blaschka is the question focused around the fact that it's a "custom field" and you already know how to do this for a standard field? Or are you asking how to generally do this using Jira Automation, less specifically about it being a custom field?

Lars Blaschka
Contributor
May 11, 2020

Hi @Jim Edgeton , 

thank you for your reply.

I know the basics of setting up automations with automation for jira. I have the ability to set a action for the linked issue by updating the custom field "expected release date". But I have no clue how to set the automation to particularly update the custom field by the end date of a sprint.

Can you help me here?

Cheers, Lars

Suggest an answer

Log in or Sign up to answer