I have a Kanban board. And my column "done" is limited to card modified the last two weeks (great feature).
When I remove a component, that trigger a change on a *lot* of cards. And since those cards become "modified", all those cards came back in the "done" column for two weeks.
How to "hide" those cards in that column?
I thought about modifying the board filter, but that change also all the graphics. Any other solution?
Expected: the card "resolved" a long long time ago are as hidden as are the card "modified" a long long time ago.
Two points came out of the conversations (thanks all!)
- The label seems indeed to be misleading: "Hide completed issues older than 2 weeks" seems to refer to "Hide completed issues updated more than 2 weeks ago".
- When deleting a component, that thus implies a change in the cards (=> "modified xxx ago")
I propose myself to add a "quick filter" on top of the board to hide "completed items" to workaround this problem:
(resolutiondate > startOfDay(-2w) AND statusCategory = Done)
OR (resolutiondate is EMPTY)
(See in "Board Settings" => Quick Filters)
This add a quick filter on top:
This filter fix the behavior, without changing any graphic...
Hi @Jean Honlet ,
To me, your case is really frustrating. The "Hide completed issues older than" feature does exactly that. It hides completed issues. Can you please share any screenshot with use? I would really like to see:
Thank you,
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is the board general setting
The change I did make is:
going to "component" => delete component => this change old card as new card. Both come back to the board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Jean!
First of all, let me say that I was wrong! This feature hides indeed all the modified issues older than two weeks (and not just the completed)!
So my proposals are:
Hope that helps :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alex, where did you find info that the sub filter algorithm also means ‘an not modified…’?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jack I don't really understand your question. But I'm sure that Jean could use the updated field to modify the results of the kanban (with all that comes with this change).
If you are referring to the "modified less than two weeks", it is stated on the kanban board on the "done" column.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes that is what I was looking for! TBH, I have never noticed that before. I probably just wasn’t being observant. Or maybe it is something new-ish? Regardless I really don’t like that feature. I like hiding issues older than via sub-filter but I don’t understand the use of modification to make issues reappear. For me, When issues are closed and old I don’t want to see them on my board even if they happen to get modified which to be honest should rarely happen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think this "update" feature is from 2018 :/
I mean you can see that Adaptavist tried to catch up with Atlassian changes [https://productsupport.adaptavist.com/browse/PCDEV-727]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's ok dude. I mean you are all over the place providing great answers! It's ok to lose some bits of info from time to time. Personally, I just found out about this feature as well. But knowledge is knowledge!
So @Jean Honlet my proposals to your problem still stand. Look up to the very first comments. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks you for all your comments and your support! Great to read :-)
So it is the correct behavior...
To avoid the whole work of a second board, I will add a quick filter on the top of the board...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jean,
I am not familiar with the behavior you mentioned - "done" column is limited to card modified the last two weeks. Is this a TMP or CMP? In TMP there is a rule to age done issues after 14d such that they are hidden from the board. I would not expect them to reappear if the old issue is modified as I would assume the underlying ‘hide’ rule is based on ‘if issue status = done for >= 14d’ and not based on ‘if issue status = done for >= 14d and last updated >= 14d’.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't know about TMP or CMP projects... Where can I find that information?
In my "Kanban board", I have this setting:
This "hide completed issues older than" is frustrating, since suddenly, the modification of all cards make them... younger than a week.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is CMP. I don’t understand why modifying done issues would make them reappear. The “hide completed issues older than” feature should not be impacted by editing a completed issue. I feel like there is something else causing this. What does your main filter look like? Are you sure the only thing being modified is removal of a component? Also, why are you modifying closed issues at all?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks.
Modifying old issues is a side effect of deleting a component. If the component is associated to old issues, they became "modified less than two weeks ago" ... and thus reappear...
I think the filter is "modified two weeks ago", and not "completed two weeks ago"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would like to confirm your theory in your last sentence. Why do you think that other than observation here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great: I like to be challenged - that bring us closer to the truth :-)
Took me sometime to find out how to check my theory, but it was simple to see:
This is when I deleted my component...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.