Questions & Answers
Get your Rally questions answered.
Question
Is there a way to hide expired Iterations from drop downs?
Question posted 1/9/08 by Ken Wehking (QA-Denver)
1932 Views, 11 Comments
Title:
Is there a way to hide expired Iterations from drop downs?
Summary:
I cannot find a way to 'hide' Iterations from prior releases from displaying in the drop down boxes on Iteration Status or Defects. Eventually these drop downs will become unmanagable with dozens of Iterations.
Full Description:
On the Iteration Status screen, our drop down is filling up with Iterations from prior releases. I'm surprised that these are still showing up even after the release end date has passed. Is there a way to hide Iterations from previous releases? I notice on the Defect entry form, 'Accepted' Iterations do not appear in the drop down. I thought of deleting the Iterations, but was afraid that would impact historical metrics. I guess my expectation would be that when a Release has expired, the Iterations would hide. Although that may create complexities in trying to view them again. Perhaps there should be a new Iteration State of 'Hide'? They could be displayed on the Schedules > Iterations tab, but when the Iteration State or Release State is 'Hide', they will not appear in drop downs on other screens.
Comments
This is a really good point. I think that internally at Rally we have not yet dealt with the accumulation of a large number of iterations in our dropdowns because we have down some re-organization of our projects from time-to-time. But I can imagine that with a long-running project/team, the iterations could really begin to add up and become a nuisance on some screens.
With that said, we don't have any concrete plans to hide iterations based on their state (as you mentioned, "accepted" or "hidden"), but I can tell you that we are doing a lot of thinking around how the UI can adjust to accommodate views of current, future and past iterations or releases. Changes that we make in regards to this will likely impact the scenario your described.
Thanks for your feedback.
Katrina
Reply to this Comment
I agree with Ken. The iteration dropdown will become really long after a year or so. So even if you don't add filtering, you will need to be sure the dropdown will scale to handle a large number of iterations.
Reply to this Comment
In about a months time we have over 20 iterations (Multiple products, multiple teams, multiple purpose sprints...like hot-fix and bug bash sprints). Soooooo... let's see if it holds up another month.
Reply to this Comment
Along this line, how is the default iteration that is displayed under a project on the Iteration status page set and is there any way to change it? I have looked around and cannot find anywhere that you can set a default iteration. I would like to set it to the main iteration we are currently working on.
Reply to this Comment
If you all haven't done so already, I'd recommend commenting on and voting up the related post for hiding old iterations in the Feature Request hive.
Rich, by default the current iteration on the Iteration Status dashboard is chosen based on dates. If you have overlapping iterations this isn't as straightforward and unfortunately, there isn't a way to specify a default for this view. There is an existing feature request to allow custom views on the dashboard pages that would help with allowing you to choose your filters. Take a look at the post here.
Reply to this Comment
Its just plain frustrating to see iterations that are "done". If they've been accepted, and I'm planning or working, I don't need to see them. An archive or "hide" flag would really be nice
Reply to this Comment
Bumping this back up...
Reply to this Comment
Is this item still under consideration as a core enhancement? Our list of iterations is growing and getting hard to manage at times.
Reply to this Comment
What's the latest status on this? Surprised to see this issue filed way back in 2008 and it's still a problem in mid-2010.
We have weekly iterations, and now even in a second release with a new set of iterations, I'm seeing the iterations from past releases in the drop down.
Reply to this Comment
Hi Trevin,
In the Questions hive this post resides in, our developers do not normally come back with status updates. Unfortunately there is not a process to check the formal status of a specific request, but you can always come back to the Feature Request post to see the vote totals, what other customers have been saying, and comments from other Rally employees.
If anyone would like to review, vote, or comment on the feature request related to this question, please visit this link - http://agilecommons.org/posts/3668ca586b
To see what our developers are currently working on, and what may be coming in the near future, please visit our Work In Progress page, here - http://agilecommons.org/pages/c11b1b38a3
Regards,
Kyle
Reply to this Comment
This feature is tracked here, and I've noticed that the request has been around since 2008 -- long before my company was a Rally customer. I'm surprised to see that this relatively easy filter hasn't been done yet!
http://agilecommons.org/posts/3668ca586b
Reply to this Comment