This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Staff-Projects/JIRA-Retool"

From OWASP
Jump to: navigation, search
(Milestones)
(Milestones)
Line 27: Line 27:
 
* 2019-3-6, Add new required fields to reimbursement tickets [Harold Blankenship] <span style="font-weight:bold;">DONE</span>
 
* 2019-3-6, Add new required fields to reimbursement tickets [Harold Blankenship] <span style="font-weight:bold;">DONE</span>
 
* 2019-3-8, Modify JIRA workflows (Reimbursement Requests) [Harold Blankenship] <span style="font-weight:bold;">DONE</span>
 
* 2019-3-8, Modify JIRA workflows (Reimbursement Requests) [Harold Blankenship] <span style="font-weight:bold;">DONE</span>
* 2019-3-13, Create new Contact Us [Harold Blankenship] <span style="font-weight:bold;">In Progress</span>
+
* 2019-3-13, Create new Contact Us [Harold Blankenship] <span style="font-weight:bold;">DONE</span>
 
* 2019-3-18, Create New Event Request tickets [Harold Blankenship] <span style="font-weight:bold;">In Progress</span>
 
* 2019-3-18, Create New Event Request tickets [Harold Blankenship] <span style="font-weight:bold;">In Progress</span>
 
* 2019-3-20, Update Workflow Status Messaging [Harold Blankenship]
 
* 2019-3-20, Update Workflow Status Messaging [Harold Blankenship]

Revision as of 04:07, 15 March 2019

Overview

This project will optimize the OWASP Foundation JIRA funding reimbursement and approval processes with the result of improving processes for all tasks submitted into JIRA. The processes will be retooled to achieve a documented Service Level Agreement (SLA), ensure responsible parties have better visibility to expected actions, reduce further requests for information, reduce unnecessary email traffic, and ensure those who submit tickets have more accurate information on status.

Project Links

JIRA Funding Requests

OSD Workflow Redesign

Goals

  1. SLA for completed ticket by others sent to budget owners no longer than 72 hours
  2. SLA for completed ticket to reimbursement no longer than 21 days
  3. Reduce the number of approvers/signatures required for common requests
  4. Properly set expectations with those submitting reimbursements
  5. Create reporting to community on SLA metrics
  6. Add other services to JIRA service desk
    1. Chapters
    2. Events

Milestones

  • 2019-2-1, Change SLAs to reflect 72 hour initial response and 21 days to close [Harold Blankenship] DONE
  • 2019-3-1, Add initial New Chapter Request [Harold Blankenship] DONE
  • 2019-3-6, Add new required fields to reimbursement tickets [Harold Blankenship] DONE
  • 2019-3-8, Modify JIRA workflows (Reimbursement Requests) [Harold Blankenship] DONE
  • 2019-3-13, Create new Contact Us [Harold Blankenship] DONE
  • 2019-3-18, Create New Event Request tickets [Harold Blankenship] In Progress
  • 2019-3-20, Update Workflow Status Messaging [Harold Blankenship]
  • 2019-3-22, Update wiki reflecting SLA expectations and approval changes [Harold Blankenship]

Leadership