Resolution Date Filter Not Working for Spikes in Kanban Board Column

[lkingsley]

I am using a Kanban board and the filter query specifies to include unresolved issues OR Done issues if they were completed in the last 2 weeks (filter query below).

The filter query works fine for Stories but not Spikes.  Spikes show in the done column when the status is done regardless of the date (I noticed that Spikes also do no show the slash through the JIRA # like Stories do, so perhaps this is the root of the issue).

Is there anyway to get my board to behave like I want for stories AND spikes?  I don't want completed items that are older than 2 weeks appearing in the board.

Filter = 

labels = config AND (resolution = Unresolved OR resolution = Done AND resolutiondate >= -14d) ORDER BY Rank ASC

[Petter Gonçalves]

Hello lkingsley,

Can you confirm if the Spikes issues are properly configured with a valid resolution (Not Unresolved)?

Please, note that your filter query is related to the resolution field and not to the Status field, so it seems that your Spikes issues are not being properly filled with a valid resolution value when transitioned to the Status Done.

This is a very common mistake when configuring new custom issue types and workflows.

If my shot is correct, you can follow the instructions on the documentation below to properly set the resolution field to your issues:

Set resolution of an existing issue

[lkingsley]

Hi Petterson,

Thanks for your reply and the article.  I do see that the completed Spikes have a status of done (or cancelled)  but a resolution of unresolved. 

The article mentions the fix as a a change to the workflow.  However, I am wondering if we can just fix the configuration of the spike itself as the Spike seems to be configured incorrectly (resolution value is apparently = unresolved).

-Lika

[Petter Gonçalves]

Hello Ikingley,

In order to change the resolution field of an issue, I recommend you to perform the procedure mentioned in the article and create the "loop" transition in the issue to perform the bulk update.

If you add the resolution field to the edit screen and simple edit the resolution for the wrong issues, the field will become editable in all the status of your issues. Since the resolution is a required field, it will cause your open issues to wrongly receive a valid value to the resolution field if any user edits it, even before it is transitioned to the status DONE, causing a problem similar to the one you are facing now.

[lkingsley]

Gotcha.  I will have to hand this over to our admin, but thanks for your help!

[Petter Gonçalves]

You are welcome!

Please, let us know if your Admin faces any questions regarding the steps in the documentation.