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

[jaylward@…]

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

[Remy Blank]

-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.

[jaylward@…]

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.

[anonymous]

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

[Remy Blank]

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

[ebray]

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.

[jaylward@…]

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)

[Christian Boos]

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