Using post function to assign ticket to sprint

[Amy Cufflin]

I have set up a post-function so that when a ticket is moved to the status "Refined", it will be moved into a sprint called "Refined - TA", with the sprint ID 6076. I set up the post function to update custom field "Sprint" to value 6076.

When I actually update a ticket (currently sitting in a sprint called "To be refined") to status "Refined", the ticket itself shows as having been added to the correct sprint, but it actually disappears from the current sprint but does not appear in the new one. If you click through from the ticket to the associated sprint, it is instead appearing on a board for a different, unrelated project, which does not have a sprint with the same name or ID.

When I change the status, I see a notification that says:

“Changes saved, but Issue not visible
For an issue to be visible, it must match your project and filters, and have a status that’s assigned to the board”. This suggests that there are filters in place, but the board filter is just project = TA".

Could anyone please advise as to what might be going wrong and how to correct it? 

Many thanks

Amy

[Amy Cufflin · Accepted solution]

hi there

For anyone following this or coming to it in the future... I worked out the answer!

The problem was that the status was not mapped to the sprint board. Even though the tickets in the "Refined" sprint will not need to be displayed on the active sprint board at any time, it transpires that by not having the status mapped to the board, it does not show up on the backlog either. So I mapped it to "to do". It -quite correctly - does not appear on the board, as it is not in the active sprint, but it does now appear on the backlog.

Thank you to those who offered advice!

Amy

[Trudy Claspill · Accepted solution]

Hello @Amy Cufflin 

Please show us the details of your post functions.

[Amy Cufflin]

Update custom field.

Issue Custom Field: Sprint

Custom Field Value: 6076 

I also tried Custom Field Value: "Refined - TA" but the result is the same.

There's nothing else on that screen to share.

[Trudy Claspill]

I was able to use the same post function to set the Sprint field to the ID of a planned (not active or completed) sprint.

Did you check the box in the post function to append the value? I did not.

Is the target sprint active, completed, or not started?

How did you determine the ID for the target sprint?

[Amy Cufflin]

I didn't check the "append" box.

Target sprint is not started.

To get the sprint ID, I did a search on all issues in that sprint, and the JQL replaces the sprint name with the ID.  (I changed the  sprint name to "Refined - TA" to ensure the name was unique, as there are lots of sprints from other projects called just "Refined"). I used the ID in the post function, and the ticket I moved to "refined" status then shows the correct sprint name (see screenshot).

. 

[Trudy Claspill]

Hm. So, it does show the correct sprint in the issue details.

But in your original post you said

"If you click through from the ticket to the associated sprint, it is instead appearing on a board for a different, unrelated project, which does not have a sprint with the same name or ID"

So, in your image above if you click on the "Refined - TA" sprint link, you end up in another board, not the one where you created the Refined - TA sprint?

If you so an issue search for all the issues in the Refined - TA sprint, does it include any issues from that other board/project?