Over the course of the last year my group has worked through a lot of projects. As projects go through cycle the list of boards continues to grow. I understand how to hide projects from view, but I don't see a way to archive old boards. I would like to be able to do this as I do not want to lose the sprint history, but the list of boards to search through is becoming obnoxious. Any suggestions as to how to hide old boards without deleting them? We are currently using JIRA 5.2.8.
Right now there is no button to hide them. There is an improvement request for this created here:
There is also a workaround in one of the comments there which, even sort of sloppy, could work:
Suggested workaround: restrict the permissions of the filter that the board is based on. The "Agile" drop-down menu and "View on Board" remain visible but a user without permissions to use the filter won't be able to see any boards based on it.
Resurrecting an old discussion here, but...
We can archive releases so they don't pollute ongoing work as a real history is built up.
This should be the same for boards for consistency so if you want to dig into the history you can, but they don't get in the way of navigating through live projects / boards.
Doesn't look like the same issue to me, as that is controlling access by user account / group for security against live boards. Not archiving boards in general.
So is there a separate feature or future feature for board archiving?
As an admin, I can switch the permissions to just myself, solves it for others, but not for me...
What I have found to be my current "work around" is to document the board filter and configuration settings and then just delete the boards. Since the boards are all just views into the records driven by the filter, you don't lose anything by killing them, and you can always recreate them in the future if necessary. It's sort of an annoyance to my type-A bookkeeping brain, but isn't the worst thing since I can keep a configuration ledger, so to speak. This issue no longer causes me much, if any, pain.
Now, what would be useful is a favorites gadget (similar to the favorite saved filters gadget) for boards, such that I could access them from a dashboard. The recently viewed list gets overwritten too often, so that options is not perfect by any stretch. Additionally, I have many groups now that use rapid boards in various ways, and hiding them under the "Agile" link is a bit confusing as they wouldn't think to look there without training and repetition of use. To them it is just a small list of "project work boards" and they much prefer to operate in their team dashboard space where things are consolidated and customized to their preferences as a one-stop-shop. Finding boards through the Agile list is just an unnecessary extra step for many. I have some groups literally bookmark their boards in their browser favorites - that is not a good sign in terms of accessibility and ease of use! This is one of those things where it won't seem like a big deal to some, but there are "old school" users who don't want too many bells and whistles - they just prefer simplicity. Everyone knows the "number of clicks to find what I want" rule.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG