Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

JIRA Audit Notes

Possible things to change:
<ul>
	<li>remove regular user permission for fields that should not be edited except by core team:
	<ul>
		<li>due date, fix versions (used for release assignment), patch, approval</li>
		<li>this will cause the fields to simply not appear on data entry screens</li>
		<li>implies creation of &quot;core&quot; group that still do have these permissions</li>
		<li>RH - yes</li>
	</ul>
	</li>
	<li>remove all time tracking features other than release assignment
	<ul>
		<li>RH -ok</li>
	</ul>
	</li>
	<li>fix default assignment (think things get assigned to project owner, currently Rich)
	<ul>
		<li>RH - yes please</li>
	</ul>
	</li>
	<li>create some components
	<ul>
		<li>language/docs/??</li>
		<li>if not, then mask out component field</li>
		<li>RH - let's wait and see what makes sense
		<ul>
			<li>How will contrib libs work?</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>make sure assignment can only be done by core team
	<ul>
		<li>again, wat about contrib libs?</li>
	</ul>
	</li>
	<li>run the re-index (apparently necessary but makes JIRA temporarily unavailable)</li>
</ul>

Design Notes

<ul>
	<li>be mimimalist: we are trying to spend our time innovating in Clojure, not JIRA!</li>
	<li>capture existing Assembla data with fidelity</li>
	<li>capture Relevance best practices across a variety of ticketing systems</li>
	<li>avoid language that presumes defects (or even software)</li>
	<li>state names represent motion toward goal (usually)</li>
	<li>states are almost implied by roles</li>
	<li>don't stay open, or re-open: use references</li>
</ul>

Basic Workflow

Issues

<ul>
	<li>name choices
	<ul>
		<li>vetted ~ ready for dev, approved for dev</li>
		<li>accepted ~ OK</li>
	</ul>
	</li>
	<li>mechanisms for prodding for action
	<ul>
		<li>no equivalent to showcase</li>
	</ul>
	</li>
	<li>does it all work in JIRA?
	<ul>
		<li>JIRA out of the box not even close</li>
		<li>I am reduced to hand-editing XML already. Seems to work, but ouch!</li>
	</ul>
	</li>
	<li>Can JIRA enforce workflow constraints?</li>
	<li>Where does this get documented?</li>
</ul>