Edgewall Software

Opened 14 years ago

Closed 14 years ago

#7667 closed defect (duplicate)

ticket properties show in different places when creating a ticket and editing a ticket

Reported by: jaylward@… Owned by:
Priority: normal Milestone:
Component: ticket system Version: 0.11-stable
Severity: trivial Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


The Properties section of the ticket should be consistent whether I'm editing or creating.

It's odd to see the properties move around once I've submitted the ticket

Attachments (0)

Change History (7)

comment:1 by Remy Blank, 14 years ago

-1 for me. I would even say that it's better that way, compared to e.g. Bugzilla: properties displayed as text are much more readable than properties displayed as editable fields. Having editable fields when entering a new ticket, and text when displaying an existing ticket (and editable fields at the bottom) is consistent with that.

comment:2 by jaylward@…, 14 years ago

that's not what I'm talking about. I'm only talking about the editable portions.

When creating a new ticket, the "assign to" field isn't there. after the ticket is created, the "assign to" field is put in as the first field in the editable section which effectively switches the column of all the fields as they were displayed when creating the ticket.

in effect, all the fields in the left column during create now show on the right during edit, and all the fields that were in the right column on create show on the left column for edits.

comment:3 by anonymous, 14 years ago

oops, I meant to say the assign to field isn't there on edit, as it's moved to the "action section"

comment:4 by Remy Blank, 14 years ago

Ah, I see. It does make sense now. Thanks for the clarification.

comment:5 by ebray, 14 years ago

I still don't see this is as an issue. The thing is that some fields may or may not be available depending on where the ticket is in the work flow, or what level of permissions the person editing the ticket has. We use a plugin that adds or removes even more fields depending on the workflow.

I don't think it's that important that the positions of the fields be consistent, because if you're doing anything more sophisticated than using the default tickets, it becomes pretty difficult to police this.

comment:6 by jaylward@…, 14 years ago

well, I would expect plugins to maintain a decent ordering on there own as I expect trac to maintain decent ordering. I don't see how plugins have anything to do with this ticket. I'd assume that properties added by a plugin would be placed at the end of the list. If trac maintains a normal property listing, then plugins would follow suit naturally (I'd hope)

comment:7 by Christian Boos, 14 years ago

Resolution: duplicate
Status: newclosed

This has already been requested several times, see #7018.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.