Tibetan and Himalayan Library - THL

<h3 class="heading-h6"><a name="THLToolboxhomegtWorkflowIssuesgtJIRATaskbasedManagementSystemUserGuide" class="anchorpoint"></a><a href="/tools/wiki/home.html">THL Toolbox</a> > <a href="/tools/wiki/Workflow%20Issues.html">Workflow Issues</a> > JIRA Task-based Management System User Guide</h3><p class="paragraph"> </p><h3 class="heading-h1"><a name="JIRATaskbasedManagementSystemUserGuide" class="anchorpoint"></a>JIRA Task-based Management System User Guide</h3><p class="paragraph"><strong class="bold">Contributor(s)</strong>: David Germano </p><h3 class="heading-h2"><a name="Overview" class="anchorpoint"></a>Overview </h3><p class="paragraph">JIRA is a browser-based bug, issue, task and defect tracking system, and project management software solution created by the <span class="nobr"><img src="/" alt="external link: " title="external link"/><a href="http://www.atlassian.com/software/jira/" target="rwikiexternal">Atlassian company</a></span>. We at THL are using this internally to register and track the progress of various work issues relating to both technology and scholarly content. The great thing about such systems is that they allow for the organized supervision of thousands of tasks across multiple individuals, including a permanent record that can be consulted in the future. Thus staff can easily retrieve all tasks assigned to them, including filtering them by project and priority. Management can easily see the status of each task, change assignments, and so forth. We also use the system for participating scholars who are doing intensive work with THL. See the THL installation of JIRA at <span class="nobr"><img src="/" alt="external link: " title="external link"/><a href="https://jira.lib.virginia.edu/secure/Dashboard.jspa" target="rwikiexternal"><img src="/" alt="external link: " title="external link"/><span class="nobr"><a href="https://jira.lib.virginia.edu" target="rwikiexternal">https://jira.lib.virginia.edu</a></span></a></span>, though it is only open to those who have accounts. </p><h3 class="heading-h2"><a name="Issues" class="anchorpoint"></a>Issues</h3><p class="paragraph">The basic category in JIRA is an "issue", which is a discrete work task entered into the system. To create an issue, click on "Create New Issue" on the top navigation bar. The first step is: </p><ul class="star"><li><strong class="bold">Project</strong>:</li> <li><strong class="bold">Issue Type</strong>: fix bug or link add feature, task, and many other options.</li></ul><p class="paragraph">Once you specify those two, you come to the main screen for describing the issue: </p><ul class="star"><li><strong class="bold">Summary</strong>: this is more like a "title" that summarizes the task for at a glance recognition</li> <li><strong class="bold">Priority</strong>: needs immediate fix, major but can't be resolved, minor, purely experimental. We simply use these as 4 levels of priority, such that functionally we understand as high, medium high, medium and low respectively. IMMEDIATE FIX should be reserved to public bugs, or urgent things that must be addressed immediately. It conveys that everything else should be dropped to address this issue. MAJOR BUT CAN'T BE RESOLVED then is to be used for the current work focus for the person in question - say the next couple of weeks. MINOR are the things that are around the corner, to be addressed in a few weeks. PURELY EXPERIMENTAL then is for things that currently we do not have immediate plans to address.</li> <li><strong class="bold">Due date</strong>:</li> <li><strong class="bold">Components</strong>:</li> <li><strong class="bold">Affects Version/s</strong>:</li> <li><strong class="bold">Fix Version/s</strong>:</li> <li><strong class="bold">Assignee</strong>: specify the person who should do the work.</li> <li><strong class="bold">Reporter</strong>: the person assigning this task</li> <li><strong class="bold">Environment</strong>: as relevant, specify the operating system/version, browser system/version, etc.</li> <li><strong class="bold">Description</strong>: this is where all the detail on the task goes.</li> <li><strong class="bold">Original estimate</strong>: this is mandatory, so if you don't know, just put 1m (one minute)</li> <li><strong class="bold">Attachment</strong>: if you have an attachment, like a screen snapshot, etc.</li> <li><strong class="bold">Impact-Effort Rating</strong>: (1) high impact: low effort, (2) low impact: low effort, (3) high impact: high effort, (4) low impact: high effort.</li></ul><p class="paragraph">Once an issue has been created, then you will find that when you open the issue, on the left hand side menu there will be a section on "available workflow actions" and a section on "operations".</p><p class="paragraph">Available workflow actions begin with: </p><ul class="star"><li><strong class="bold">Resolve Issue</strong>: this gives options for resolution - unresolved, fixed, won't fix, duplicate, incomplete, can't reproduce - and allows you to add a comment.</li> <li><strong class="bold">Close Issue</strong>: this allows you to add a comment, but otherwise simply changes the issue from "open" to "closed".</li> <li><strong class="bold">Start progress</strong>:</li></ul><p class="paragraph">If you choose "Resolve issue", the workflow actions menu will change to: </p><ul class="star"><li><strong class="bold">Close Issue</strong>:</li> <li><strong class="bold">Reopen Issue</strong>: this allows you to reopen an issue that was marked as fixed and/or closed.</li></ul><p class="paragraph">Once you close, then only "reopen issue" will remain as an available workflow operation.</p><p class="paragraph">As you do various workflow operations, the "status" indicator automatically changes: </p><ul class="star"><li>open, in progress, reopened, resolved, closed, deployed to test server,</li></ul><p class="paragraph">Operations include the following options: </p><ul class="star"><li><strong class="bold">Assign this issue</strong>:</li> <li><strong class="bold">Attach file to this issue</strong>:</li> <li><strong class="bold">Attach screenshot to this issue</strong>:</li> <li><strong class="bold">Clone this issue</strong>:</li> <li><strong class="bold">Comment on this issue</strong>:</li> <li><strong class="bold">Create sub-task</strong>:</li> <li><strong class="bold">Delete this issue</strong>: delete the issue.</li> <li><strong class="bold">Edit this issue</strong>: edit the content ofthe issue.</li> <li><strong class="bold">Link this issue to another issue</strong>:</li> <li><strong class="bold">Move this issue</strong>:</li> <li><strong class="bold">Convert to sub-task</strong>:</li> <li><strong class="bold">Voting</strong>: You cannot vote for an issue you have reported.</li> <li><strong class="bold">Watching</strong>: Watch it to be notified of changes</li> <li><strong class="bold">Worklog</strong>: this allows you to log work done on the issue.</li></ul><p class="paragraph"> </p><h3 class="heading-h2"><a name="ResolvingampClosingIssues" class="anchorpoint"></a>Resolving & Closing Issues</h3><p class="paragraph">For the person doing the work, they should "resolve" it when done - never close it. Then the person who is checking the work, they need to "close" it. Thus its important that the "reporter" be the person who is checking the work. And it is essential that the "reporter" then actually confirm the work is done by "closing" it.</p><p class="paragraph">It is important if you are doing the work and you report it, that you change the reporter to someone else if someone else is going to need to check the work. If in fact no one else is involved, and it is an item you discovered and you fixed, so that no one else needs to check, then please you have to be responsible for CLOSING it and not simple RESOLVING it.</p><p class="paragraph">We need to close issues each week, so that a simple query across "all projects" for all "resolved" issues will turn up the things that need review, and not a laundry list of things done weeks ago.</p><p class="paragraph">Also notice that you can "save" filters you use in searches to avoid having to manually redo them. </p><h3 class="heading-h2"><a name="ClassifyingIssues" class="anchorpoint"></a>Classifying Issues</h3><p class="paragraph">JIRA has multiple ways to categorize issues. Firstly, there is a three fold way to categorize issues by subject matter - Category, which contains Projects, which contains Components. In THL, we have only one Category, which is THL itself. We then have a number of Projects, which are broad classifications such as "Administration", "Place", "Literature", and so forth. These then form larger containers, with which we have various THL work initiatives that are rendered as "Components". Thus within the "Places" project, we have components of "Sera Monastery", "Drepung Monastery", "Place Dictionary", and so forth, each of which is a distinct THL initiative involving a number of different work tasks at any given point. We can easily make more "components", but to make new projects we have to ask for the help of the Library staff.</p><p class="paragraph">THL Projects are as follows: </p><ul class="star"><li>THL Administration</li> <li>THL Community</li> <li>THL Documentation</li> <li>THL Education</li> <li>THL Encyclopedia</li> <li>THL History</li> <li>THL JIATS</li> <li>THL Literature</li> <li>THL Multimedia</li> <li>THL Places</li> <li>THL Reference Content</li> <li>THL Tibetan Language Learning</li> <li>THL Tools</li> <li>THL Tourism</li> <li>THL XML Text Publishing Tech</li></ul><p class="paragraph">In addition, to projects and components, there are two other ways you can link tasks to each other.</p><p class="paragraph"><strong class="bold">Sub-tasks</strong>: this is available when viewing an issue and is available in the left hand OPERATIONS menu as "create sub-task". A sub-task is just like an issue in most ways, and gives the same interface. Please note the issue-type is hard-wired as "sub-task". Once made, it will visually appear as a subordinate for its parent task. This is a very convient way to group together items.</p><p class="paragraph"><strong class="bold">Link Issues</strong>: this is available when viewing an issue and is available in the left hand OPERATIONS menu as "link this task to another task". This allows you to add a comment, to specify the issue it is linked to, and finally to use a drop down list to specify how the two are linked: </p><ul class="star"><li>is a pre-requisite for</li> <li>is dependent on</li> <li>duplicates</li> <li>is duplicated by</li> <li>incorporates</li> <li>is incorporated in</li></ul><p class="paragraph"> </p><h3 class="heading-h2"><a name="CheckingonIssuesOpenforyouorforaGivenperson" class="anchorpoint"></a>Checking on Issues Open for you or for a Given person</h3><p class="paragraph">Click on "Find Issues" from the top navigation bar and then fill out your criteria. In this way you can see all the open issues assigned to you, resolved issues done by someone else, or whatever else you need to see. </p><h3 class="heading-h6"><a name="ProvidedforunrestrictedusebythespanclassnobrimgsrcsakairwikitoolimagesicklearrowgifaltexternallinktitleexternallinkahrefhttpwwwthliborgtargetrwikiexternalTibetanandHimalayanLibraryaspan" class="anchorpoint"></a><em class="italic">Provided for unrestricted use by the <span class="nobr"><img src="/" alt="external link: " title="external link"/><a href="http://www.thlib.org" target="rwikiexternal">Tibetan and Himalayan Library</a></span></em></h3>