What's the best way to mark tickets as "not ready" in the backlog

[Kevin R_ Raney]

I'm using a next-gen kanban board and I would like the ability to mark tickets as "draft or not ready" when they are in the backlog and prevent those tickets from being moved to the board.

I thought about adding a new first column, but i don't want to waste space on the board and that seems like the only way to add a new usable status. 

[Mirek]

Better than trying to find a scheduled restart mechanism, try to avoid not needed restarts. I know that from time to time is good to free up some resources but JIRA should be stable enough to avoid restarts. Number of users do not only count when speaking about performance. There are other aspects that may be important. Try starting from looking at your infrastructure and JVM settings. 

[Christopher Lederer]

Hey Mirek

I do understand your view-point. But my question is rather, has anybody such a schedule in place?

I can just by cross checking monitoring see that there is a relation between performance and last re-start.

Its not that we have a lot of issues - rather the opposite.

Just want to see how the "general" community is seeing this. Of course maintenance and care on underlying infra and JVM is certainly a good hint. Consider that we have resources and expertise to have any eye on that.

In simple words - would you recommend a regular re-start - every week, month etc.... as a practice of maintenance?

[Nic Brough -Adaptavist-]

I would not recommend a restart at all. You should really be investigating why there are problems and fixing the root cause. I would recommend a regular maintenance cycle - i.e. upgrading, and restarting during that. A number of my clients do have regular restarts in place, but in most cases, they have discovered that all they're doing is hiding a deep rooted problem. It's a bit like plastering over the cracks in the wall at home, only to realise too late that you've got a subsidence problem. Frequency of restarts depends on how often you're having the issue. As a temporary measure, establish when faults are occurring and simply schedule something a little more frequent. Then you can investigate your real issue.

[Mirek]

As I mentioned already.. try to avoid not needed restarts. I do not recommend it as a practice of maintenance. Nic bring up one of the reasons why it is not a good practice.