I think that the ticket date begin/end option has to be limited to users, for example with access controls.
I can find a reason why a user with a problem has the possibility to assign a begin and end date to its ticket, while it makes more sense to let project administrators to assign its.

Comments

samuelet’s picture

samuelet commented
Version: 6.x-1.9 » 6.x-1.15
Magnity’s picture

Magnity commented
Version: 6.x-1.15 » 6.x-1.x-dev
Status: Active » Postponed (maintainer needs more info)

The date begin field is not required, so a user can set it blank or simply use the default (current date), which I think is sufficient in most use cases.

Unless there are significant opinions otherwise, I am considering a "Won't Fix" for this.

andrewjohns’s picture

andrewjohns commented

Along similar lines, it would be nice to customise the ticketing system. Assuming that this was used in a sort of help desk scenario, where your users were customers, you wouldn't necessarily want/need them to fill in things like the duration of the ticket, the cost, and so on. That they can leave it blank is a workaround, but isn't ideal because a cluttered interface is a usability issue. I guess you can add the "status" as a hidden field - if they're submitting a ticket then it's "inserted", no other options are needed.

Assuming that there are no plans to support this, how would I go about removing such options for standard organisation users, but as admin I would see the full interface? Actually I guess I could use CSS to hide everything, but that's not exactly ideal.

Magnity’s picture

Magnity commented
Component: Code » Storm Ticket
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Won't fix for core subject of issue.

@andrewjohns - please create a new issue for your request - it isn't 100% related to this issue.