OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

csaf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (CSAF-8) Document CSAF TC best practices for issue processing workflow


     [ https://issues.oasis-open.org/browse/CSAF-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Hagen updated CSAF-8:
----------------------------

    Proposal: Proposed best practices for issue processing uploaded to kavi at https://www.oasis-open.org/committees/download.php/59455/tc-csaf_issue-processing-workflow_states-and-transitions.pdf in revision 2016-11-25 (alternate URL: http://bit.ly/csaf_best_pract_issues )  (was: This issue is not ripe for resolution, but adding some textual description and guidance to the processing might easily complete this.

Visual display (cannot attach to issue in that JIRA version/setup) ... at:
https://www.oasis-open.org/committees/download.php/59451/tc_flow.png

The bare bones directed graph in dot language:

digraph tc_wf {
	NEW -> OPEN -> RESOLVED -> APPLIED -> CLOSED;
	OPEN -> DEFERRED -> OPEN -> CLOSED -> OPEN;
	RESOLVED -> OPEN;
	NEW -> CLOSED;
	NEW -> DEFERRED;
	APPLIED -> RESOLVED;
}

The workflow as a dot language file (used for the diagram at https://www.oasis-open.org/committees/download.php/59451/tc_flow.png ):

Please cf. https://www.oasis-open.org/committees/download.php/59452/oasis-jira-tc-states-and-transistions-verbs-semantic-20161125.dot (for now)
)

> Document CSAF TC best practices for issue processing workflow
> -------------------------------------------------------------
>
>                 Key: CSAF-8
>                 URL: https://issues.oasis-open.org/browse/CSAF-8
>             Project: OASIS Common Security Advisory Framework (CSAF) TC
>          Issue Type: Task
>            Reporter: Stefan Hagen
>            Assignee: Stefan Hagen
>              Labels: request_tc_discussion
>
> We should document some best practices that we will agree on for issue processing.
> Based on the offering already configured in JIRA the following (attached states and transitions) already work for some TC's quite well and offer a balanced work load when adhered to for members and editors alike, while enabling effective and efficient work queue planning (for analysing, resolving and applying alike. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]