cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Kinard <>
Subject Re: Proposal: Change JIRA to have bugs as "unassigned" by default
Date Thu, 19 Sep 2013 16:09:38 GMT
This sounds like a solution to workflow issue. But what is our workflow?

So if I understand correctly, the proposal is that a new bug that is unassigned means it has
not been triaged.

What would Jira state be for the following:
- triaged and nobody plans to work on it yet (low priority)
- triaged and person X plans to work on it, but they haven't started yet (person X's to do
- triaged and person X plans to work on it, and they have started (in progress)

And do these states need to be captured in Jira or is that overkill?

Is it expected that the component owner does all the triage-ing?

On Sep 18, 2013, at 11:00 PM, Andrew Grieve <> wrote:

> Motivation:
> It's impossible to know whether new bugs have been looked at by the default
> assignee.
> Rationale:
> Setting it to <unassigned>, means new bugs will be obviously "untriaged".
> Once assigned, it will mean someone intends to work on it.
> This won't eliminate bugs that get assigned and then not fixed in a timely
> fashion. I think that's okay though. It'll be an improvement anyways.

View raw message