Jira automation - create story and assign it to the sprint when sprint is started

Jakub Stephan December 20, 2022

Hi.

 

I want to create a story in newly started sprint with subtasks.

 

Issue creation working fine along with subtasks.

I can not assing it to the active/future or {{sprint.id}}

 

I have error in audit log:

 

```

ACTION DETAILS:
["10203"]
CREATE ISSUE
Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Sprint (customfield_10020)
Issues created successfully
CCT119-53
CREATE SUB-TASKS
Successfully added sub-tasks
CCT119-54, CCT119-55, CCT119-56, CCT119-57, CCT119-58
```

2 answers

1 accepted

1 vote
Answer accepted
Marta Woźniak-Semeniuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 20, 2022

Hey @Jakub Stephan 

Did you try to just add it from the backlog after creation, by dragging it into the sprint?

 

From the log it looks like you have some problem with Field with id 10203 - can you check what field is that? 

Below is how to find it.

Login as JIRA adminstrator,  click  the admin  button  Issues > Custom fields, there is a button at the top right had side of every custom field when you click it you will see Configure | Edit | Translate you can click any of this then you will have a link like this

https:JIRAurl/secure/admin/EditCustomField!default.jspa?id=15800

then change this number to the one you know 10008 so it will be like this
https:JIRAurl/secure/admin/EditCustomField!default.jspa?id=10008

you will be in the interface of this custom field.


There is another way but time consuming, you can press F12 on your keyboard,
click on inspect from the developer view of your browser(lets say fire fox mozila)
then iterate over custom field window in JIRA by moving cursor of you mouse
to every custom field name until you find the one that has the number 10008

Jakub Stephan December 20, 2022

Custom field is correct, it's mapped with Sprint.

ConfigureCustomField default.jspa customFieldId=10020

When story is created i can manually move that to the sprint without issues.

History:

 

Jakub Stephan
 updated the Sprint 5 seconds ago
None -> JIRA_TEST Sprint

Marta Woźniak-Semeniuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 20, 2022

Can you show how the automation is setup ( a printscreen)?

Jakub Stephan December 20, 2022

Here is my automation flow (read from the bottom to up):

 

Zrzut ekranu 2022-12-21 o 08.07.41.pngZrzut ekranu 2022-12-21 o 08.07.32.pngZrzut ekranu 2022-12-21 o 08.07.27.pngZrzut ekranu 2022-12-21 o 08.07.21.png

Marta Woźniak-Semeniuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 21, 2022

1. Could you try replacing "JIRA_TEST Scrum Board" in Sprint field on Issue creation with smart value {{sprint.id}} ?

2. Could you try if the rule would work with either of the way of setting the sprint just for issue creation without the subtasks? This way we might get the information if the problem lies in the subtasks creation or the main issue creation :) 

Jakub Stephan December 21, 2022

I have the same issue without subtasks defined. I guess that not a case.

 

Also with using {{sprint.id}} it's failing.

 

Zrzut ekranu 2022-12-21 o 09.57.57.png

 

 

Audit log:

Zrzut ekranu 2022-12-21 o 09.57.11.png

Marta Woźniak-Semeniuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 21, 2022

Okay, weird question time :) 

When you create an issue in a usual way, using the "Create" button, do you also have Sprint field in the create screen?

Like Jakub Stephan likes this
Jakub Stephan December 21, 2022

Thats the point! 

 

I was shocked that it might be an root case :(

 

Thanks for you suggestion.

 

I was missing this field on issue creation screen.

Marta Woźniak-Semeniuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 21, 2022

Great! Glad I could help :) 

JIRA is a very interconnected system, sometimes tracking a problem makes you feel like a detective :) 

Have a good day Jakub

Like Jakub Stephan likes this
0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 20, 2022

Hi @Jakub Stephan 

For a question like this, please post images of your complete automation rule and the audit log details showing the execution.  Those will provide context for the community to offer suggestions.  Thanks!

Until we see that...I suspect you are either missing a branch statement or the trigger used doesn't support what you need.

Kind regards,
Bill

Jakub Stephan December 21, 2022

Understand.

 

I had some issue with new question form, that i was not able to upload any pictures. Now it's possible within new replies.

 

I've attached screens in other replies to @Marta Woźniak-Semeniuk . Would you like ot check that as well?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 21, 2022

No need for that; it appears that Marta has helped identify the cause.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events