Module : Tickets
Issue |
Type |
TrialGrid Version |
Description |
|---|---|---|---|
3855 |
Feature |
68 |
Custom objects can now be added as related objects to Tickets. |
3576 |
Bug |
60 |
A race condition can occur where a user can add the same user 2x to a ticket if the network is slow. A user with this double-assignment could not be removed without an error. This has been corrected. |
3382 |
Bug |
53 |
When opened from the sidebar of a related object, tickets did not offer search in the related object drop-downs for Draft, Type and Object Name. This has been corrected. |
3339 |
Bug |
51 |
When opened from the sidebar of a related object, tickets did not show their descriptions. This was corrected. |
3336 |
Bug |
50 |
Project ticket page has error if there are related objects in soft-deleted Drafts. This was corrected. Objects in soft-deleted Drafts are no longer shown. |
3291 |
Bug |
49 |
Creating a ticket with a title longer than 400 characters would fail with a system error. The system now allows titles up to 1000 characters. |
3290 |
Bug |
49 |
If a ticket had a title longer than 200 characters then the system would fail with an error while trying to create a notification that a user was assigned to the ticket. This was corrected. |
3161 |
Bug |
47 |
If the text of a ticket contained very long text with no text breaks, the text would overflow the display box. This was corrected. |
3113 |
Bug |
44.3 |
When an ticket is created, if project roles are assigned as part of the initial Ticket save then the users with that role were not notified of their assignment. Roles added to a ticket after creation were notified correctly. This was corrected. |
2924 |
Feature |
41 |
When users are assigned to a ticket by role, all users with that role in the project now receive a notification email and an in-system alert. |
2560 |
Feature |
39 |
Tickets can now be assigned to a URL Role. |
2737 |
Feature |
37 |
Tickets now track who closed them and the closure date/time. This data appears in listings and printed/exported listings. |
510 |
Feature |
37 |
When a user is assigned to a Ticket they will receive an Alert notification and an Email (unless the user is assigning themselves, in which case no notifications will be sent). |
2726 |
Feature |
37 |
When a user is removed from a Ticket they will receive an Alert notification (unless the user is assigning themselves, in which case no notifications will be sent). They will not receive an Email notification. |
2734 |
Feature |
37 |
There will be a warning if there are unsaved changes to a Ticket and you try to navigate to another page. |
2735 |
Feature |
37 |
The Ticket 'Assign Yourself' button will be disabled if you are not in the Project Team and are not the Project Owner. |
2727 |
Bug |
37 |
PDF exports from the Project and User ticket lists were not correctly formatted. This was corrected. |
2641 |
Feature |
34 |
In the Object Editor and Ticket activity lists you can sort by latest activity last (the default) or latest activity first. |
2557 |
Feature |
34 |
The New Ticket page now has the same appearance as the Edit Ticket page. Previously the New Ticket page was a simplified page allowing entry of only Title, body and a due date. |
2558 |
Feature |
34 |
Tickets may now be created directly from object editors (e.g. when editing a Form). The ticket created this way is automatically associated with the object being edited. |
2335 |
Feature |
34 |
Duplicate of #2558. |
859 |
Feature |
34 |
Duplicate of #2558. |
2559 |
Feature |
34 |
Tickets related to objects may now be edited directly from the editor for that object. e.g. When editing a Form, tickets related to the Form can be edited in a pop-up window. |
2564 |
Feature |
34 |
Tickets and comments use Markdown syntax to display plain text with formatting such as bold or to create headings and tables. Our Markdown syntax removed newlines from content. Newlines are now preserved in Tickets and Comments. |
2565 |
Feature |
34 |
The "Edit Ticket" button which initiates editing of the heading or body of a ticket has now been changed to a pencil icon which comments also use |
2566 |
Feature |
34 |
When opening a ticket from the Object Editors, or creating a new Ticket the pop-up window had a Close button to make it clear how to dismiss the window. |
1673 |
Feature |
16 |
It is now possible to select a TestCase from the Ticket editor to be related to the Ticket. This is the same mechanism as is used for Forms, Custom Functions etc. Test Cases may still have links to Tickets via the @ticket:ticket_number text in the Test Case script. The @ticket reference method was retired in September 2021. |
1631 |
Feature |
16 |
When there are no tickets associated with Test Cases the Related Tickets column is hidden in the Test Cases list. |
1541 |
Feature |
16 |
The Ticket list now has a comment count column. |
1181 |
Feature |
13 |
Tickets now have an optional Due date field. |
1185 |
Feature |
13 |
In Ticket listings tickets which are Open and past due show their due date in red text. |
1078 |
Feature |
13 |
Tickets may be closed and re-opened. |
920 |
Feature |
9 |
Users ticket list now includes the related Project in the listing and all ticket lists show related Objects. |
695 |
Feature |
6 |
A count of open Tickets associated with each Draft Object type are now shown in their list. |
511 |
Feature |
6 |
Tickets associated with an object are displayed in the object summary slide-out area. |
670 |
Feature |
6 |
Users with the new permission Can Comment are now able to comment on Tickets. Comments are formatted in the Markdown syntax and can include references to Project wiki pages, other tickets using the #<ticket_number> and other users using the @username syntax. Users who are @mentioned in this way will receive an alert message in the application but also an email notification that they have been mentioned with a link to the location of the ticket/comment. |
636 |
Feature |
4 |
In Wiki and Ticket pages, typing #<number> to reference a ticket by its number now pops up a listing of tickets starting with that number (e.g. #1 -> #1, #10, #11, #12...#100..) This makes it easier to ensure that the correct ticket is referenced. |
621 |
Feature |
4 |
Markup syntax for tickets and wiki pages has been made identical. As part of this change, existing Wiki pages were converted to the new Markdown syntax. Users can now reference tickets by number in ticket text and in wiki pages (e.g. #123 is rendered as a link to ticket #123) |
450 |
Feature |
2 |
Added Tickets feature. |