tigefa4u projects Trac

TicketQuery macro returns now ''No results'' when the query doesn't match any ticket (except in ''count'' mode where it shows 0 as usual). Closes #3293.

Added ticket cloning feature (#4686)

The ''Clone'' button is placed in the ticket box, next to the ''Reply'' one.

Note that this request uses a ''post'' method and not a ''get'' because using ''get'' doesn't work well with IE and Opera (previewing or saving a cloned ticket will fail).

Though there's no special right needed besides TICKET_CREATE, this feature is mainly useful only for TICKET_ADMINs that have to track the same issue in different line of development, so the feature will only be available to them.

Add an up link back to parent resource, on attachment and attachment list pages. Fixes #4701.

Remember #2703 and the reply-below.diff? Well, here's another try. This is also to be consistent with the upcoming change adding more inline buttons to the description area.

Improved rendering of the Ticket preview, which now better matches the one of the Wiki preview.

Improved the layout of the ticket preview

So far, the preview was redirecting to the change preview block, which was at the bottom of the ticket ''Change History'' block. While this had the merit to show the change entry in the place it will take after the change is saved, this was a bit far away the top of the page, which also contains useful informations for the preview:
- the occasional warnings in case of problems with the change
- the new values for the ticket fields, among which the ticket description

Therefore, I moved that change preview block upward, just above the ticket box.

Refactor the ticket change display into a template macro.

WorkFlow: warn about some special ''action'' keys used for non-workflow related tasks.

WorkFlow: follow-up to r5447, the check for conflicting controller changes was done too late in _do_save. Do it earlier and make sure it's done only once.

Previewing or saving a new ticket or ticket changes won't trigger an error when there are some problems with the changes. Instead, it will revert to previewing mode along with one warning for each particular issue.

This addresses the #1146 issue as well as the #4100 one, as the user provided data can't be lost anymore.

All the validations are now done in the `_validate_ticket` method.