CTSC:JIRA harmonization meetings.051109

Back to Collaboration:Harvard_CTSC

Harvard Catalyst JIRA Meeting Minutes May 11, 2009

• JIRA CONFIGURATION

1.) each form has its own project
2.) each project belongs to the category called ‘Catalyst Consulting’
3.) workflow
a. steps will be ‘open’, ‘reopened’, ‘closed’
4.) Notifications
a. Remove ‘reporter’ from notification schemes since this will be the system in our case.
b. Please see accompanying Excel spreadsheet of notifications.
5.) Permissions
a. Triage person will have the ability to create a task in any of the projects. (except the research navigators projects)
b. Triage person will have the ability to move a task into any of the projects. (except the research navigators projects)
c. Triage person will have view access to any of the projects (except the research navigators projects)
d. Research navigators have ability to view tasks in other projects, create tasks in other projects, pull tasks from other projects to their own, and move tasks from their project into other projects
e. Moving tasks from one project to another will require massaging the data a bit, since the custom fields vary slightly
6.) custom fields
a. priority field will be (high, med, low)
b. issue type will be (task).
7.) Default issue navigator will have (this can be changed by the user):
a. Priority icon
b. Issue key
c. Summary
d. Assignee
e. Institution
f. First name
g. Last name
h. Created date
i. Updated date
8.) Default Dashboard
a. List of issues assigned to logged in user.
b. Favorite filters
c. Project summary info
d. Breakdown by open/closed
e. Breakdown by priority
f. Breakdown by assignee
9.) Default filters
a. All issues
b. All open issues

• LOGISTICS related

1.) rollout will be in the order that the webforms were deployed
a. biostats
b. genetics
c. imaging
d. claim data
e. health disparities
f. research ethics