WI0003-02: Redmine Configuration and Usage Flashcards
WI0003-01: Redmine Configuration and Usage
What does this indicate when the ticket is created for “Warranty”?
These are quality failures that were implemented on a live production client site. A ticket cannot be Warranty until after it has been implemented.
WI0003-01: Redmine Configuration and Usage
What does this indicate when the ticket is created for a “Maintenance”?
Generally involves site updates, server maintenance, or related.
WI0003-01: Redmine Configuration and Usage
What does this indicate when the ticket is created for “Support”?
The client raised a concern or question for which the resolution does not involve implementing new or changed code or configuration. An investigation may be needed; however, the solution does not include functional changes.
What does this indicate when the ticket is created for “Support”?
WI0003-01: Redmine Configuration and Usage
How is ticket priority determined?
A combination of priority and its due date. A ticket without a due date should be the last worked on for that priority level.
WI0003-01: Redmine Configuration and Usage
When LE assigns a ticket to a Developer. What MUST be included in the ticket?
The LE assigns and should include time estimates, priorities, the LE, and a well-defined ticket scope.
WI0003-01: Redmine Configuration and Usage
What is the difference between the “Client Due Date” field and “Due Date”?
The client’s due date is used to communicate a delivery deadline to production and is communicated to/from/with the client. The due date is for internal prioritization.
WI0003-01: Redmine Configuration and Usage
What parties generally have access to tickets?
Clients and internal personnel are given rights to create, view, and edit tickets within the client project.
WI0003-01: Redmine Configuration and Usage
Can information in a ticket be kept internal?
Yes. The ticket has a “Private” flag that is ticket-wide. And, when commenting, there is a “Private” flag that can be set that hides that particular comment.
WI0003-01: Redmine Configuration and Usage
Where is the scope of the ticket defined?
The scope is defined in the ticket description. It may be a small piece of a more extensive set of tickets, in which case Confluence and parent tickets may provide additional context. Discussions in ticket comments may elucidate other facets or features that contribute to ticket scope.
WI0003-01: Redmine Configuration and Usage
How is the scope for “normal” and “creative” design tickets defined?
For normal tickets, the scope should be fully defined when the developer starts work. For creative design tickets, scope is expected to changed throughout development. The scope can change no further once a ticket is sent for QC.
WI0003-01: Redmine Configuration and Usage
Should a ticket ever be re-opened?
Never, ever, ever, ever, ever, Peter Pan. Never. Let me say that again. Don’t ever do it. Don’t even think about it.
WI0003-01: Redmine Configuration and Usage
What information should be contained in the “time entry” comments?
A brief one-liner note about work performed during that time.
WI0003-01: Redmine Configuration and Usage
Are the comments on the ticket required to be filled out?
These are not always required but should inform LEs or sometimes clients of progress, and current status which would indicate where to test, where to look for code, and things to be aware of.
WI0003-01: Redmine Configuration and Usage
What happens when development of a ticket is completed?
The status is set to “Pending QC,” Due date is set for two business days from completion, and assignee is set to unassigned, unless a) otherwise informed, or b) returning to QC after they’ve requested changes.
WI0003-01: Redmine Configuration and Usage
When QC is complete, what updates are made?
The status is set to “Pending LE Review,” the Due date is set for two business days from completion, and the assignee is set to the LE noted on the ticket.
