<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Max,<br>
<br>
I've merged that to article. <br>
<span id="comment-body-1474">
<div class="jive-rendered-content">
<p>Another Idea <img src="cid:part1.08070004.02030501@exadel.com"
height="16" width="16"></p>
<p>Lets state that relevant commit should have not <strong>JIRA issue
ID</strong> but <strong>URL</strong>. That saves time, because it will
shown like a link in:</p>
<ul>
<li>in Fisheye</li>
<li>in google reader</li>
<li>in mail clients</li>
</ul>
</div>
</span>WDYT<br>
<br>
Denis<br>
<br>
Max Rydahl Andersen wrote:
<blockquote cite="mid:49F5A160.7060409@redhat.com" type="cite">It's a
wiki - feel free to update it :)
<br>
<br>
/max
<br>
<br>
Denis Golovin wrote:
<br>
<blockquote type="cite">Max Rydahl Andersen wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
While working on various issues I noticed that there is a growing
tendency to forget setting the fix version on resolved jira's.
<br>
<br>
By not having a fix version on resolved jira's our changelog's we use
for announcements are not correct nor is it easy
<br>
to see when an issue is fixed since you have to manually go in to SVN
and retrace what release the specific commits
<br>
went into.
<br>
<br>
Thus please remember to set the fix version when resolving something as
Done!
<br>
<br>
And to anyone doing QA please don't close resolved issues that does not
have a fix version - reopen them.
<br>
<br>
As a reminder here is the wiki that describes the workflow for JBoss
Tools jira <a class="moz-txt-link-freetext" href="http://www.jboss.org/community/docs/DOC-12834">http://www.jboss.org/community/docs/DOC-12834</a> </blockquote>
Max,
<br>
<br>
I'd add in Fixing/Resolving part:
<br>
<br>
Keep description updated - which means if issue has a discussion what
actually should be done all this should be collected in description.
That saves time for anyone who is working with this issue to understand
what actually should be done and how to verify it. Last thing is useful
for QA.
<br>
<br>
Demo screencast and relevant screenshots - add screencast or
screenshots to show new functionality and mark it as Documentation
affected or "New and noteworthy" to give a doc team to know there is
something to add in "New and Noteworthy" or add/change in
documentation.
<br>
<br>
Thanks
<br>
Denis
<br>
<blockquote type="cite">/max
<br>
_______________________________________________
<br>
jbosstools-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a> </blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>