[Dev] default redmine issue states

Brett Gilio brettg at posteo.net
Thu Jul 12 20:46:54 GMT 2018


Bill,

So, the procedural order here would be for somebody to file a report 
with the "pending" or "unconfirmed" label. It would then be picked up by 
a privileged user to either reassign it a label, or confirm it and 
assign either themself or another privileged user to the task?

If so, I think this sounds like a solid idea, assuming that the other 
privileged users are on-board.

Brett Gilio
brettg at posteo.net | bmg at member.fsf.org
Free Software -- Free Society!

On 07/12/2018 09:18 AM, bill-auger wrote:
> the default state of a redmine issue is currently the extremely
> uninformative 'open' - it would be nice if these issue states were more
> semantic and used more optimally - i would like to propose that the
> default state of a redmine issue opened by a user to be 'unconfirmed' -
> then a privileged user could confirm the issue as a bug or freedom
> concern and set its state to 'confirmed' or 'in-progress' and assign it
> to the appropriate person, or set to 'info-needed' or 'invalid' if it
> can not be easily confirmed - it is not difficult or dangerous to manage
> these states - redmine makes it convenient to create, view, and manage
> these states via the web
> 
> 
> 
> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
> 



More information about the Dev mailing list