I really miss this features which is already present in Jira Software.  

I think it should be embarrassing to Attlasian team, that the issue is 3 year old and noone has even touch it. This does say a lot about their "care".

I believe this issue is a duplicate of JWMCLOUD-19 – Ability to configure Core board to show issues for more than 14 days and remove issues before 14 days

I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!

Agree this is a must have 

I didn't notice this in my initial testing, and now I need to switch to a software project because of it. Major oversight.

This is a must have for team wellbeing, seeing the progress of "done" tickets can be as valuable as the backlog. Also helps to remember what actions were taken against those completed tickets at a glance. Having to use a separate filter for this result is very disjointed

And having an option to delete resolved tickets manually like in Jira Software would be useful as well. How this works is  completely inconsistent between the different Jira project types.

This is a must-have feature to be able to set it to Never or whatever date in the history you want to see the Completed issues on the Board. This is frustrating to have them disappear just like that.

Please add this feature

Ah yes, it's so great to be using Beta software, hopefully this feature is finished with Jira finally releases it's first version!

It is quite important to have this feature.

Thanks,
Wagner

the option to configure the timeline would be fine.

also the headline of the "summary" should be adoptet.

As if the done issues are removed after 14 days the Headline of the summary should be some kind of "progress in last 14 days" and NOT "project progress". 
last suggests, that the summary shows the overall progress - which by now is not so, and wrong information
--> external auditors dont know about the 14 days shedule !

at all not perfect. and sould be corrected in short time.

either it shows 14 days ( with correct heading) or it shows project progress as named correctly (overall). an option to configure this would be find. standard in my opionion should be overall progress.

This seems very much linked to the behavior of the Summary page that I submitted and is in 'gathering interest' status.  

In case anybody hasn't noticed yet, it's worth checking the link below, as the limitation applies to the Summary page pie chart as well.

https://jira.atlassian.com/browse/JWMCLOUD-257

Why is this even different for every project type?!

• In Team Managed JWM its fixed to 2 weeks
• In Team Managed Software Project there is a button "Clear done issues" in the "Done" Column
• In Company managed Software you can set it to never, 1, 2 or 4 weeks but you can't do it manually
• I don't even bother to check Company managed JWM...

This is insane and completely confusing.

Guys, this is causing a serious problem for our team. We use kanban for simplicity and all issues in done are disappearing. We are unable to track them.

The board is configured with plenty of integrations. Just give us an option to change the 14 days, like in company managed project where we can set never!

I strongly agree that this should only be down to the user to control full aspects of each card rather than Jira auto-removing itself.

This issue is hampering our organization's adoption of Business projects usage. Our business users wish to have the option to see resolved issues even after 14 days of them being resolved. We also noticed that a similar (14 days resolved) filter is applied on List, Calendar and Timeline views of Business Projects, but all 3 of those views also have (via ... More) option on the top right, the option to 'Show/hide done items', such toggle does not exist in Board view unfortunately. There is also no text anywhere in the Board screen to indicate that any issues are hidden. And there seems to be no workaround currently. Please fix this.