Comments
-
This should help - https://aws.amazon.com/quickstart/architecture/jira/
-
It really depends on what you're looking to report. * You can use Dashboard Gadgets in Jira, some of which can be based on filters. * For a more comprehensive reporting solution, eazyBI tends to be the add-on of choice. * When all else fails, you can export a JQL query as a CSV and create your own reports based off this.
-
For both the ACP-100 and ACP-300, I did the following... I first read the Jira documentation (back-to-front) for versions: * 6.4 * 7.X Not to mention, I brushed up on my JQL. Then, I read two books: * Jira 7 Administration Cookbook by Patrick Li * JIRA Strategy Admin Workbook by Rachel Wright Now, I've been using Jira…
-
I've personally read (cover-to-cover): * Jira 7 Administration Cookbook by Patrick Li * JIRA Strategy Admin Workbook by Rachel Wright For me, I used the Cookbook more as a reference guide, almost like a 101 for admins, while the Workbook was definitely more practical, with battle tested examples of what to do in specific…
-
@Chris Blyth - good point. Portfolio for Jira has a dependencies report which shows this more clearly, however in Jira Software, you'll have to drill into the individual card view and look at the 'Link' section.
-
Jira considers work in a Sprint done when it is dragged to a status mapped to the right most column of a board. Usually, this status/column will be called 'Done'. 'SB-1071', in the screenshot above, is in a status called 'Testing' which may not be in the right most column of your board.
-
If you're using Time Tracking in JIRA (and have it mapped to your issue type/screen), you should see a roll-up of estimated time versus time spent and time remaining. See below:
-
To play it safe, first create a copy of your original workflow, associate it to your project and modify that going forward. First things first, a status of "Won't Fix" will do nothing on it's own. Think of it more like a label or a way of filtering when searching for issues. To get the resolution of "Won't fix" to be…
-
For a crude workaround, you could create a custom field called "Percentage completed" and get team members to manually enter the percetnage completed for a task. From there, you can export a number of issues to a CSV file, using JIRA's filters, and then use a few spreadsheet functions to get the report you like. Otherwise,…
-
Is it possible to see/visualise the number stories completed within an epic/feature or another level of abstraction (e.g. inititative) in Portfolio for JIRA? That is, the metric I'd like to visualise is the number of issues completed within a parent issue.
-
From my experience, the progress bar only works against estimated Issues in JIRA as opposed to the number of Issues complete. For example, if you have 4 issues in an Epic with only one estimated and only that estimated Issue is complete (i.e. the rest have yet to be done), the progress bar will show 100% complete.
-
Most Agile teams I've worked with will map their requirements as follows: * (Epic) User Story = Epic (in JIRA) * (Sprint-Ready) User Story = Story (in JIRA) * Task = Sub-task (in JIRA) The intent... The intent behind this is, when requirements are first created, they are nebulus and Epic in size (i.e. they take longer than…
