Purpose
The goal is to collect features we know we use in ST- so the project can evaluate if they are available in RT.
The results have been fed into
STToRTInvestigationFactorsAssessment which supersedes this information.
Collecting votes: "Critical" "Important" and "Nice to Have"
- Add new items as headings. Please don't edit existing headings, because other people will have already voted.
- Add votes ("Critical" "Important" and "Nice to Have") - and comments such as "Critical, including a URL for uploaded files" - as bullet-points below each heading. You don't have to sign your comments because edit history is tracked.
Tracking time spent, with a convenient interface (ie, not editing the total time worked)
- Nice to have
- Critical
- Critical
- Critical
- Critical
- Critical
- Critical
- Critical
Ability to view all tickets in queue, not just ones you're involved with
- Important
- Critical
- Important
- Critical
- Critical
- Critical
- Critical
- Critical
Ability to view all tickets belonging to a CSCF group
Ability to view all tickets belonging to a project (user definable) group
Item dependencies and see-also
- Important
- Critical
- Critical
- Critical
- Critical
- Critical
- Critical
- Critical
Ability to create and update tickets via email
- Nice to have
- Critical
- Important
- Nice to have
- Critical
- Critical
- Important
Batch dependency creation with particular fields set to arbitrary values
- Nice to have
- Important
- Nice to have
- Nice to have
- Nice to have
- Nice to have
- Important
- Nice to have
Flexible search; if possible, ability to include SQL (eg., Fraser will fine-tune search query with SQL wildcards such as "evergreen%MC%3007"
)
- Important
- Nice to have
- Important
- Nice to have
- Nice to have
- Nice to have
- Important
- Important
API so our inventory system can continue to report on related work items
- Important
- Critical
- Important
- Important
- Nice to have
- Important
- Important
- Important
Custom field, for subscription code, that we can easily extract work-hours on particular codes, and replicate the ST functionality within the "subscriptions" database.
- Nice to have
- Important
- Nice to have
- Important
- Critical (or some other method, eg by queue)
- Critical (or some other method)
- Important
- Nice to have
Recording data to allow budgeting / managing spending using cost-estimate (and keywords and dependency trees - such as summing cost-estimates including dependencies)
- Important
- Important
- Nice to have
- Nice to have
- not important
- Important
- Important
- Important
Attachments to related documentation- uploading files, links to files for external use, and external file links.
- Important
- Critical
- Critical
- Important
- Important
- Critical
- Critical
- Important
Command-line access to perform searches and updates
- Nice to have
- Important
- Nice to have
- Nice to have
- Nice to have
- Important
- Nice to have
- Nice to have
Direct access to the uploaded attachments, eg., smbmount
- Important
- Important
- Important
- Important
- Important
- Important
- Important
- Nice to have
Auto lookup barcodes in inventory and hostnames in inventory and DNS, fill in corresponding info and room number, warn on typos, canonicalize hostnames, link barcodes and hostnames to inventory
- Critical
- Critical
- Important
Auto lookup users and email addresses, canonicalize, show real name, link to WatIAM, warn on typos
Handle simultaneous update by multiple users of multiple fields in the same request without locking or losing updates
Sort search results by due date, date created, or last acted (or any field displayed)
Arbitrary SQL searches (e.g. date_created>unix_timestamp()-3600*24*7 and subject like '%print%') with ability to bookmark and API (e.g. needed for Bill's run-on sentence)
- Critical
- Critical
- Important
Arbitrary choice of columns and their order and optional abbreviation in search results with ability to bookmark and API
- Important
- Nice to have
- Important