Tickets
Tickets are worklist items which can be assigned to users and labelled with different workflow states. They can be used for Specifications, To-Do items and any other type of activity where tracking tasks is important within a Project.
Tickets can be assigned to individual users who have a role in the Project Team and/or to a URL Role. When a Ticket is assigned to or removed from an indidivual user, they will receive an email (unless they have turned off receiving email nofications in their TrialGrid user profile). When a Ticket is assigned to a URL Role, the users in the Project with that Role will not be notified by email. If you wish to notify the users with a certain URL Role you can '@mention' the role in a Ticket comment (see below).
Tickets can be associated with:
CRF Draft Objects such as Forms, Data Dictionaries etc.
Labels which can be used to track workflow states
See also
Task Lists
Ticket descriptions support task list checkboxes using Markdown syntax. To create a task list, use the following format:
- [ ] An incomplete item
- [x] A completed item
- [ ] Another incomplete item
Numbered lists (1. [ ] First step), quoted lists (> - [ ] Item), lists with a blank line between items,
and items nested under other items all work the same way. Start a list on a new line after a blank line: a
- [ ] line directly under a line of text is part of that paragraph, not a list, so it has no checkbox.
Each item will be rendered with an interactive checkbox. Clicking a checkbox will toggle its state between complete and incomplete without needing to edit the Ticket description. When a checkbox is toggled, an activity record is created showing which item was marked as completed or incomplete.
If someone else has changed the Ticket description since you opened the Ticket, ticking a checkbox does not change anything. The current description is shown instead, so you can check it and tick the box again.
Comments do not show task list checkboxes.
A user must have Comment permission to toggle checkboxes.
Generating Documents
If your URL has Document Templates with a scope of Project Tickets, a "Documents" button appears at the top of the Ticket list.
The generated document reports on the Tickets currently listed, so narrowing the list first narrows the report. It receives every Ticket matching the search box, the Label filter and the assignment filter ("All", "Unassigned" or "Assigned to me"), together with which page of the list you are on (Open, Closed or All). Those filter values are passed to the Template as well as the Tickets themselves, so a document can state how it was filtered.
Note
The Ticket list has no row checkboxes, so a report always covers everything currently listed rather than a subset you have picked out. Reports run from a Draft object listing behave differently — there you can select individual rows, and the Template receives both the selected objects and the listed ones. See Draft Object List Template Context.
Comments
A user with Comment permission may add a comment to a Ticket. Like 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.