<html>
<head>
<base href="https://wiki.asterisk.org/wiki">
<link rel="stylesheet" href="/wiki/s/en/2176/25/9/_/styles/combined.css?spaceKey=AST&forWysiwyg=true" type="text/css">
</head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="https://wiki.asterisk.org/wiki/display/AST/Issue+Tracker+Workflow">Issue Tracker Workflow</a></h2>
<h4>Page <b>edited</b> by <a href="https://wiki.asterisk.org/wiki/display/~mjordan">Matt Jordan</a>
</h4>
<br/>
<h4>Changes (4)</h4>
<div id="page-diffs">
<table class="diff" cellpadding="0" cellspacing="0">
<tr><td class="diff-snipped" >...<br></td></tr>
<tr><td class="diff-unchanged" >This is a submitted bug or new feature (with patch!) which has yet to be worked either by an Asterisk community developer or by a developer at Digium Asterisk developer, but appears to be a valid bug or new feature based on the description and provided debugging information. <br> <br></td></tr>
<tr><td class="diff-changed-lines" ><span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">{note}</span> <span class="diff-added-words"style="background-color: #dfd;">{info}</span> <br></td></tr>
<tr><td class="diff-unchanged" >An issue can also be in the *Reopen* state, indicating that it was closed but reopened for some reason. This state is semantically the same as *Open*. <br></td></tr>
<tr><td class="diff-changed-lines" ><span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">{note}</span> <span class="diff-added-words"style="background-color: #dfd;">{info}</span> <br></td></tr>
<tr><td class="diff-unchanged" > <br>h3. In Progress <br></td></tr>
<tr><td class="diff-snipped" >...<br></td></tr>
<tr><td class="diff-unchanged" >Severity levels can be selected for an issue and may be viewed by bug marshals as a way to categorize issues for priority; however, a high priority does not necessarily entail that any bug marshal will treat that issue with any greater urgency. <br> <br></td></tr>
<tr><td class="diff-changed-lines" ><span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">{note}</span> <span class="diff-added-words"style="background-color: #dfd;">{warn}</span> <br></td></tr>
<tr><td class="diff-unchanged" >The *Blocker* severity may be used by bug marshals as a way to indicate that the Asterisk developer community has decided that an issue is of such critical importance that it should prevent release of an issue. In general, this status should be used sparingly and may warrant discussion on the issue tracker if assigned to an issue. Issue reporters should not select the *Blocker* severity. <br></td></tr>
<tr><td class="diff-changed-lines" ><span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">{note}</span> <span class="diff-added-words"style="background-color: #dfd;">{warn}</span> <br></td></tr>
<tr><td class="diff-unchanged" > <br>h1. Notes <br></td></tr>
<tr><td class="diff-snipped" >...<br></td></tr>
</table>
</div> <h4>Full Content</h4>
<div class="notificationGreySide">
<h1><a name="IssueTrackerWorkflow-Overview"></a>Overview</h1>
<p>This document describes how issues move through the <a href="https://issues.asterisk.org/jira" class="external-link" rel="nofollow">Asterisk Issue Tracker</a>. It is most beneficial for Asterisk bug marshals; however, it is also good reading for anyone who may be filing issues or wondering how the Asterisk Open Source project moves issues from filing to completion.</p>
<h1><a name="IssueTrackerWorkflow-IssueTrackerWorkflow"></a>Issue Tracker Workflow</h1>
<p>The workflow in the issue tracker is handled in the following way:</p>
<ol>
<li>A bug is reported and is automatically placed in the <b>Triage</b> status.</li>
<li>The Bug Marshall team should go through bugs in the <b>Triage</b> status to determine whether the report is valid (not a duplicate, hasn't already been fixed, not a tech support issue, etc.). Invalid reports should be set to 'Closed' with the appropriate resolution set. Categories and descriptions should be corrected at this point.
<div class='panelMacro'><table class='noteMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/wiki/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td>Issues should also have enough information for a developer to either reproduce the issue or determine where an issue exists (or both). If this is not the case then the issue should be moved to 'Waiting for Feedback' with the appropriate information requested. See <a href="/wiki/display/AST/Asterisk+Issue+Guidelines" title="Asterisk Issue Guidelines">Asterisk Issue Guidelines</a> for more information on what an issue should have before it is accepted.</td></tr></table></div></li>
<li>The next step is to determine whether the report is about a bug or a submission of a new feature:
<ul>
<li>BUG: A bug should be moved into the <b>Open</b> status by clicking <em>Acknowledge</em> if enough information has been provided by the reporter to either reproduce the issue or clearly see where an issue may lie. The bug may also be assigned to a developer for the creation of the initial patch, or review of the issue.<br/>
If a patch has been created for the issue, it is acceptable to modify the summary with the text "<a href="/wiki/pages/createpage.action?spaceKey=AST&title=patch&linkCreation=true&fromPageId=3702839" class="createlink">patch</a>" to indicate that a patch is available for the issue. At this point, initial code review and discussion about the patch will take place, either on the issue or on <a href="https://reviewboard.asterisk.org" class="external-link" rel="nofollow">Review Board</a>. One the patch has been sufficiently reviewed, the patch can be committed by a developer and the issue closed.</li>
<li>FEATURE: New features must be filed with a patch. As such, the issues can be immediately moved into the <b>Open</b> status by click <em>Acknowledge</em> and be reviewed for adherence to <a href="/wiki/display/AST/Coding+Guidelines" title="Coding Guidelines">Coding Guidelines</a> and <a href="https://reviewboard.asterisk.org" class="external-link" rel="nofollow">code review</a>. From there any changes to style or feel of the patch based on feedback from the community can be discussed, and changes to the patch made. Once the feature has been accepted, or a decision has been made that it will not be merged, the issue should be <b>Closed</b> with the appropriate resolution.</li>
</ul>
</li>
<li>If at any point in the workflow, an issue requires feedback from the original poster of the issue, the status should be changed to <b>Waiting for Feedback</b>. Once the required information has been provided, it should be placed back in the appropriate point of the workflow by using the <em>Send Back</em> button.</li>
<li>If at any point in the workflow, a developer or bug marshal would like to take responsibility for doing the work that is necessary to progress an issue, the issue can be assigned to that developer and the issue moved into the <b>In Progress</b> state. At that point the developer assigned to the issue will be responsible for moving the issue to completion.</li>
</ol>
<h1><a name="IssueTrackerWorkflow-WorkflowSummary"></a>Workflow Summary</h1>
<p>The following is a list of valid statuses and what they mean to the work flow.</p>
<h2><a name="IssueTrackerWorkflow-Triage"></a>Triage</h2>
<p>This issue is awaiting review or in review by bug marshals. Categorization of the issue, summary, description, version, and other related informationshould be fixed as appropriate. See the <a href="/wiki/display/AST/Asterisk+Issue+Guidelines" title="Asterisk Issue Guidelines">Asterisk Issue Guidelines</a> for more information.</p>
<h3><a name="IssueTrackerWorkflow-WaitingforFeedback"></a>Waiting for Feedback</h3>
<p>This issue requires feedback from the poster of the issue before any additional progress in the workflow can be made. This may include providing additional <a href="/wiki/display/AST/Collecting+Debug+Information" title="Collecting Debug Information">debugging</a> information, or a <a href="/wiki/display/AST/Getting+a+Backtrace" title="Getting a Backtrace">backtrace</a> with <tt>DONT_OPTIMIZE</tt> enabled, for example.</p>
<h3><a name="IssueTrackerWorkflow-Open"></a>Open</h3>
<p>This is a submitted bug or new feature (with patch!) which has yet to be worked either by an Asterisk community developer or by a developer at Digium Asterisk developer, but appears to be a valid bug or new feature based on the description and provided debugging information.</p>
<div class='panelMacro'><table class='infoMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/wiki/images/icons/emoticons/information.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td>An issue can also be in the <b>Reopen</b> state, indicating that it was closed but reopened for some reason. This state is semantically the same as <b>Open</b>.</td></tr></table></div>
<h3><a name="IssueTrackerWorkflow-InProgress"></a>In Progress</h3>
<p>This is an issue which is currently being actively worked by an assigned developer. At this stage, it would be appropriate to have a patch being developed or attached to the issue for review.</p>
<h3><a name="IssueTrackerWorkflow-Closed"></a>Closed</h3>
<p>The issue has been resolved, and a patch has either been committed or the issue has been rejected for some reason.</p>
<h1><a name="IssueTrackerWorkflow-SeverityLevels"></a>Severity Levels</h1>
<p>Severity levels can be selected for an issue and may be viewed by bug marshals as a way to categorize issues for priority; however, a high priority does not necessarily entail that any bug marshal will treat that issue with any greater urgency.</p>
<div class="error"><span class="error">Unknown macro: {warn}</span>
<p>The <b>Blocker</b> severity may be used by bug marshals as a way to indicate that the Asterisk developer community has decided that an issue is of such critical importance that it should prevent release of an issue. In general, this status should be used sparingly and may warrant discussion on the issue tracker if assigned to an issue. Issue reporters should not select the <b>Blocker</b> severity.</p></div>
<h1><a name="IssueTrackerWorkflow-Notes"></a>Notes</h1>
<ol>
<li>Using the filters in JIRA - such as the <a href="https://issues.asterisk.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=11493" class="external-link" rel="nofollow">Triage (Supported)</a> filter is- useful for finding issues that need attention quickly.</li>
<li>The issue tracker now has the ability to monitor the commits list, and if the <a href="/wiki/display/AST/Commit+Messages" title="Commit Messages">commit message</a> contains the appropriate tag, e.g., "(Closes issue ASTERISK-9999)", the bug will automatically be closed.</li>
</ol>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;" class="grey">
<a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=AST">Stop watching space</a>
<span style="padding: 0px 5px;">|</span>
<a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
<a href="https://wiki.asterisk.org/wiki/display/AST/Issue+Tracker+Workflow">View Online</a>
|
<a href="https://wiki.asterisk.org/wiki/pages/diffpagesbyversion.action?pageId=3702839&revisedVersion=3&originalVersion=2">View Changes</a>
|
<a href="https://wiki.asterisk.org/wiki/display/AST/Issue+Tracker+Workflow?showComments=true&showCommentArea=true#addcomment">Add Comment</a>
</div>
</div>
</div>
</div>
</div>
</body>
</html>