You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Purpose:

Access Jira Handling

  • It is the responsibility of the Editors to update working text and reflect the current state of contributions submitted via Jira.  

CONTRIB, DTP contributions

ScenarioEditorContribution State Transition
Normative Contributions



Contribution gets accepted to be incorporated into a working text

Copy the Meeting report notes showing acceptance as Jira comment.

Set the Jira state of the contribution to "In-progress" and assign the ticket to the editor.

Move from For Review to In-Progress
Accepted Contribution gets integrated into working text

Update the working text and inform PS leads of the updated text.

PS leads will move the ticket from In-Progress to Completed status.

Contribution is agreed that it needs work.Copy the meeting report note as a comment and assign the ticket to the originator
Contribution is presented but not acceptedEditor copies Meeting report notes as a Jira comment.  Editor moves the contribution to "Wont Do" stateMove from For Review to Won't Do state
Informative Contributions (no target working text)

Work Area Director puts together an informative contribution (e.g., brainstorming, overview of work area, etc)
After presenting such contribution (where no action is expected), the work area director moves the ticket to completed state


YANG contributions (YMONU, YMOLT, etc)

ScenarioEditorContribution State Transition
Normative Contributions



Contribution gets accepted to be incorporated into a working text

Copy the Meeting report notes showing acceptance as Jira comment.

PS leads when merging pull requests will handle the Jira transitions (no manual intervention is needed)
Contribution is agreed that it needs work.Copy the meeting report note as a comment and assign the ticket to the originator
Contribution is presented but not accepted


  • No labels