Internal Errigal Collaboration Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Design + Usability Jira Project ======

This Jira project is for design and usability related items. In most cases these tickets are created from items noted on the [[https://docs.google.com/spreadsheets/d/1D9lqJLcUwcencptEEFBk78M_uETcbU0TuNGtHJSGogk/edit#gid=0|Snags Sheet]].

These tickets are worked through by Michelle and when a resolution/proposed design has been created, the ticket is moved to Ready for Dev. Tickets in this state can then be moved to an appropriate development sprint to be worked on by a developer.


  * **Project Name:** Design And Usability
  * **Project Key:** DESIGN
  * **Jira Board:** [[https://errigal.atlassian.net/secure/RapidBoard.jspa?rapidView=100&projectKey=DESIGN|Design + Usability Jira Board]]
  * **Ticket Template:** [[https://errigal.atlassian.net/browse/DESIGN-2| Jira DESIGN ticket template ]]

===== Priority Meanings: =====

  * **Critical** - Severely impacts customer behavior, impacts a large number of users, prevents the user from carrying out their work, major page restructure, UI re-skin etc.
  * **Major** - Has an impact on one or two users but doesn't prevent them from doing their work (some type of work around in place), more large-scale visual issues, moving larger components.
  * **Minor** - Spelling mistakes, minor visual issues, doesn't prevent the user from carrying out their work.

===== Workflow States: =====

  * **Open** - Initial starting state when new ticket is created
  * **In Progress** - working through the ticket, investigating, creating mockups etc.
  * **Internal Input Required** - need to verify something with a developer, a tester, ops, etc.
  * **Customer Input Required** - need to verify something with the customer.
  * **Ready For Dev** - Final state for tickets to be moved into the next development sprint
  * **Resolved** - if a new dev ticket to track the dev implementation, the ticket moves to this state. Tickets also move to this state if they don't require dev but some design work was still carried out.
  * **Closed** - ticket closed out with no work done on ticket.

===== Ticket Template: =====

  * **Problem Summary** - rough outline of the issue/task
  * **Background Information** -  any relevant background info. where the problem was reported, what customer reported it, how it was discovered etc.
  * **Related Tickets** - any related tickets
  * **Action Items** - todo list of things to work on as part of this ticket
  * **Proposed Design** - UI implementation with link to Mockups and/or spec documentation
  * **Unresolved Questions** - any questions that need to be answered relating to this ticket
  * **Components** - Represent affected application
Sidebar

Internal Errigal Collaboration Wiki

User Tools

Site Tools

Page Tools
