User's Issue drops from Scrum when put into closure

[Robert Symons]

I have a user on my project that can put issues into the Scrum and move them into progress, but when they move them over to either closed or resolved the issue drops off from the Scrum board and the team loses that issue and the points tied to it.

Does the issue vanish completely?  No, the issue maintains on the issue board and shows in a closure state but is no longer on the Scrum board.

[Nic Brough -Adaptavist- · Accepted solution]

What is the filter for the board?  It sounds like it might be excluding closed/resolved issues.

[Robert Symons]

I thought of that first, the problem is that it is tied to only 1 user on the scrum board and not the other 5.  Would not any filter issues impact the whole group tied to the scrum?

Also, the point value of that issue is removed from the initial point value of the sprint as if it was never attached.

[Robert Symons]

project = SIP AND summary ~ "Mission" OR label ~ "Mission" OR assignee = "User1" OR assignee = "User2" OR assignee = "User3" OR assignee = "User4" OR assignee = "User5" AND resolution = Unresolved ORDER BY cf[12430] ASC

[Jack Brickey]

Robert, i think the issue is in your filter. ultimately the way it is written I suspect is not what you intend and to be honest I'm not 100% sure what you are intending. But let me throw something out there to see if we can get this resolved.

Let me propose the following alternative:

project = SIP AND (summary ~ "Mission" OR label ~ "Mission") OR assignee in (user1, user2, user3, user4, user5)

A couple of things to note:

1. I suggest using the "assignee in" function rather than a bunch of "OR" functions
2. I don't think you want "and resolution = unresolved" since that is the resolution value for all issues prior to a status of Done.

I may be off on what you are trying to display on the board so please correct me by providing a plain text version of your intentions, e.g.

• only issue for project SIP
• AND only if they have "mission" in the summary or a label of "mission"
• OR only if the assignee is one of: u1, u2, u3...

[Robert Symons]

Thank you for your suggestion.  Not certain why but once we removed the resolution = unresolved portion of the filter his issues came back into the closed area.

It still does not explain why his was the user of the whole group that was singled out, but we are back and running again.

Thank you

[Jack Brickey]

It think it does explain it. I expected the unresolved to be the culprit. Was the suspect user in the User5 position in your filter? I suspect so. Consider the following alone...

assignee = user5 AND resolution = unresolved

as soon as an issue becomes resolved it will disappear. The “AND resolution = unresolved” was only operating on the last user.