#411 closed defect (fixed)
Edit ticket description?
| Reported by: | anonymous | Owned by: | daniel |
|---|---|---|---|
| Priority: | high | Milestone: | 0.8 |
| Component: | ticket system | Version: | 0.7 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
We're migrating over to trac from CVSTrac. In CVSTrac we could edit the initial description of the ticket so that we can correct bad wiki formatting and so forth. Its not possible to preview your ticket — so once you hit submit you're stuck with all the mistakes you made.
You can currently change the summary, it seems, but not the full description. I want to change the full description, but I have no way to do this.
I recognize that your usage of the ticket system is to put a somewhat terse one-liner into the description field, and then use the discussion to provide the details.
Although the discussion is useful to document, I prefer to summarize the results of the investigation into the description afterwards, so that you don't have to read the entire discussion — the description will be enough.
Attachments (0)
Change History (10)
comment:1 by , 20 years ago
| Milestone: | → 0.8 |
|---|
comment:2 by , 20 years ago
| Priority: | normal → high |
|---|
comment:3 by , 20 years ago
Putting the tickets under revision control sounds cool, but it seems like the revision numbers of the repository would climb like crazy because every ticket added or edited would create a new changeset. Plus, trac currently does not modify the repository at all — changing it to do so might create other problems.
comment:4 by , 20 years ago
| Version: | 0.6.1 → 0.7 |
|---|
comment:5 by , 20 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
My take on editing ticket descriptions is that it should be limited to ppl with TRAC_ADMIN privileges.
comment:7 by , 15 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
As a new Trac user, I also find this behavior suboptimal. It's been five years, please revisit this design flaw — it makes it very difficult to update a ticket summary so that others don't need to scroll through the entire comment history.
comment:8 by , 15 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | 0.8 |
| Resolution: | → worksforme |
| Status: | reopened → closed |
It's possible to achieve this in Trac 0.11 by giving the TICKET_EDIT_DESCRIPTION permission, see TracPermissions#TicketSystem.
comment:9 by , 15 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
(oops, shouldn't have cleared the milestone)
comment:10 by , 15 years ago
| Milestone: | → 0.8 |
|---|---|
| Resolution: | → fixed |
| Status: | reopened → closed |
I am in the same side. But to allow changes in the description, it would be nice if the ticket itself is under revision control.
As Trac has already integrated with subverion, some idea from below link http://subissue.tigris.org/ may make sense. Unfortunately I am not the python programmer and not able to contribute to it.