Closed (won't fix)
Project:
Storm
Version:
6.x-1.22
Component:
Storm Ticket
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 May 2009 at 10:07 UTC
Updated:
27 Feb 2013 at 15:07 UTC
Hi there,
I like this module, but as I see, it have the same error (or feature;-) like similiar others..
During adding ticket, user can choose any status from the list.
This is really annoying for companies / organizations which have external tester teams. New ticket should always have only one default status (hidden value) - "new".
The same for assigning new tickets.. - this should be hidden value set by project admin.
Is it possible to set in 1.22 or any future releases?
Comments
Comment #1
Magnity commentedI'll consider this - although because Storm uses the Drupal node system, it is possible to display "new" over any tickets that a logged in user has not yet visited anyway (although this isn't controllable - you can't set it back to new once you've read it).
Your request also overlaps slightly with #316613: Requiring fields according to role, although I suspect that these are two slightly different angles.
It would be a future release rather than 1.22, all development starts in the -dev release (which is updated fairly frequently) then a snapshot is taken to realise as a stable version every now and then.
Comment #2
cyc commentedJordiTR in that topic (comment no 3) has the same approach, but it was not commented from October 2008:-(
It would be nice to hear this feature will appear on the 'to do' list of any future release (or already is)
thanks anyway, hope my issue will not be forgotten
Comment #3
juliangb commentedThis issue will not be fixed in Storm (D6).
In D7 (Project Management), we are moving to using the fields API, which then means that you could use a module such as field permissions to restrict access.
This will be a much better solution.