#4503 Developer-only fields for tickets

unreleased
open
nobody
General
nobody
2014-11-18
2012-07-05
Chris Tsai
No

It's often not desirable to allow users to change whatever fields they want (eg., re-opening closed tickets, or changing milestones), it would be nice to be able to mark fields in the field management as only developer-editable.

It may also be useful to be able to set fields as only viewable by developers (eg. for internal tracking that may not be useful for regular users).

Discussion

  • Chris Tsai - 2012-07-05
    • summary: Developer-only fields --> Developer-only fields for tickets
     
  • Chris Tsai - 2012-07-05

    We should also consider making "owner" a developer-only field (for edit) by default. I can't really think of a case where it makes sense for a non-project-member to set who a ticket is assigned to.

     
  • Dave Brondsema

    Dave Brondsema - 2012-07-13
    • milestone: limbo --> someday
     
  • Dave Brondsema

    Dave Brondsema - 2012-07-13

    I'm hesitant to add complexity to the permission & fields configuration. Lets wait and see if this is really necessary.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2013-02-08

    Originally by: earnie

    Oh, I would consider it delightful and even necessary. I agree with Chris about the Owner field but I suppose someone else might not so we should be able to assign a permissions group as well.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2013-12-03

    Originally by: rokuingh

    The part of this ticket that is interesting to me is the ability to set fields as viewable by developers only, to track information that should not be publicly viewable (like contact info).

     

Log in to post a comment.