Closed statuses in dropdown for new issue (manager role)
The following applies to manager role when creating a new issue.
I find illogical to have closed and rejected statuses in the "new issue" status dropdown. As they are marked as "closed issue" in admin panel, I think they should be filtered, and any to be created issue would then only propose "new" or "assigned" status in the dropdown.
May I have some wrong settings ? I feel like the proposed states are the ones which can lead to "new" state, without checking whether they are closed states or not :)
I attach the manager's bug issue worklow.
The rapporter only has "new" option, while the developer has "new" and "assigned".
PS : when creating this redmine issue, I see "status" having both "new" and "resolved" options...
#1 Updated by Thomas Pihl about 9 years ago
Well, i think you have a point. But then again, i do sometimes enter issues that is already done (i just enter them for reference). In that case it would be double-work to first enter it into an open state and then change it to a closed state.
Some my customers raised same question. When they got slightly more used to redmine, the problem went away. Now they understand that they see every status they are ALLOWED to use, and have to choose.
#2 Updated by Mischa The Evil about 9 years ago
Thomas Pihl wrote:
[...] But then again, i do sometimes enter issues that is already done (i just enter them for reference). In that case it would be double-work to first enter it into an open state and then change it to a closed state.
I feel the same way about this...
#5 Updated by Dipan Mehta over 5 years ago
Ideally a 'New issue' can go to any other status as defined by the workflow. However, it is desirable that when the issue is registered it must first attain the default status (typically New) at least once! It breaks many workflow assumptions.
When a new ticket is being opened, status should not be changeable. It should be changeable only during the update.