Though it doesn't seem like the priority field is used that much (seems
like it is always at the default of major), I bulk-set the priority of
issues created in 2011 and prior to trivial to at least allow reducing
the noise a bit. Many issues might appropriately be closed. Hopefully
the Jira cleanup can do that for some.
One thought I had -- for at least the uPortal project (though arguably
the portlets as well) could we set the default priority to minor? I'd
like someone to consciously decide to make the priority major so at
least there is some level of triage that occurred and the priority field
starts to be more helpful than useless. Thoughts?
James Wennmacher - Unicon
480.558.2420
On 12/19/2013 04:42 PM, Drew Wills wrote:
Hey folks,
I want to let everyone know I'm planning to do some housecleaning in
the uPortal JIRA space.
Currently there are...
- 262 open issues; and
- 5 reopened issues
I think that's a lot to look through, should you want to review them
(I do, occasionally).
I'm betting that there are many that can be resolved/closed because...
- They're duplicates
- They can't be reproduced
- They apply to features that have been rebooted, removed, or replaced
- They _only_ apply to versions of uPortal that are no longer under
active maintenance (there's a "closed:will not fix" option for this
very situation)
I suggest that we'd be better served resolving/closing as many of
these as possible to make it easier to find and review the most
important issues. (And of course the data is all still there; you
will still be able to find historical JIRA issues that apply to
previous releases.)
Should anyone want to pitch in -- big thanks!
Should anyone have thoughts or concerns -- please send them in.
drew wills
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
