[Bf-committers] How to Manage Incomplete Tasks that have the Requested Information

[Julian Eisel]

I was thinking about proposing a similar idea some time ago, so +1 from me.
The downside would be that we don't have a way to mark reports as
being new, which is useful information. So maybe adding a new priority
'New' would make sense?

Further, I think we should only categorize a report as 'Normal' if
it's actually assigned to a developer and if there's a chance that
she/he will investigate soon. Even if we improved here already, there
are still too many old reports set to 'Normal' either assigned to
nobody or without much hope the person assigned will investigate soon.
(We might also apply this rule for 'Confirmed' reports).

Following this proposal, criterias for setting priority would look
something like this:
* New: Newly created reports, awaiting initial review
* Needs Triage: Waiting on developer action
* Incomplete: Waiting on author action
* Normal: Issue not confirmed yet but assigned to developer
* Confirmed: Issue confirmed (and assigned to dev?)

BTW, I always wondered why we have both 'High' and 'Unbreak Now!' as
priorities? They both have the same meaning in essence, so one should
be enough.

On 20 March 2016 at 19:38, Aaron Carlisle <carlisle.b3d at gmail.com> wrote:
> I have noticed that often tasks that are missing some information (a .blend
> file for example)
> and marked as incomplete seem to be forgotten if the users gives the
> requested
> information.  I purpose that these task be changed back to "Needs Triage"
> priority.
> It seems that this priority has not been used for its purpose and just used
> as a
> priority for new tasks.  However, if this priority is used for its purpose
> I think it will
> help these tasks not get lost in the bug tracker.
>
> Sincerely,
>
> Aaron Carlisle
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers