Walter Buggenhout Community Champion

Hi Joao, JIRA Software and JIRA Service desk are different products having different license tiers. If you need 25 service desk agents, you purchase a license for 25 Service Desk agents. This does not influence your 100 JIRA Software users. But indeed, as Nic says, if they are 25 additional users that you want to grant…

It's not quite clear what plugin you are referring to. But anyway, commercial add-ons on the Marketplace follow the user tier of the product you purchase them for. If your Confluence instance is 50 user, than so is your add-on.

Hi Ryan, The statistics page was indeed removed and replaced by a set of issue filters. By default, it shows the open issues, but by selecting the Switch Filter link next to the filter title, you can choose from a variety of different filters. The filters are mainly focused on open issues, recent updates or issues…

There's one thing that immediately comes to my mind; could you check whether ranking is enabled on your board? You can check this in the general configuration of the board or you can explicitly add 'ORDER BY Rank to the end of your JQL statement - given it isn't there yet already.

Hi Amanda, I guess that you will normally not be working on the epics themselves. Could you try modifying the source of your kanban board to exclude the epics?

Hi Amanda, My guess is that your kanban board currently has swimlanes based on epics. This is what is probably the cause of the grouping. To verify whether this is the case and undo it, go to the configuration of your board. Then, from the options on the left select swimlanes: Screen Shot 2016-10-06 at 17.50.56.png…

Hi Corwin, The terminology might be a bit misleading here, but "created by anyone" is not doing what you think it is. Created by anyone is just an aggregation of the tickets created by me + Where I am participant. Your customers will not be able to see each other's tickets. No worries. The default setting is that you can…

The burndown chart has more of a focus on day-to-day activities. Below the chart, you will see a an overview of updates on issues. When an issue is added to a sprint, a status change occurs or work has been logged. All these events are entries that are logged and displayed below the chart when they occur. The sprint report…

Then I'm running out of inspiration just with this information. Could you share a screenshot of your sprint health gadget and active sprint board? Ideally the column configuration of your board.

And is your closed status green (statuscategory = done)?

Do your closed issues have a value in the resolution field?

Hi Casey, Basically nothing. You log work against issues, not against a sprint. So as long as you don't delete your issues or the work logs against them, they just remain in the system on the date you originally logged them.

JIRA has a built in field called workratio which compares the original estimate vs time spent. You could create a filter saying: Project = xxx And workratio > 100 This would give you all issues where time spent was more than the original issues. 100 stands for 100%, btw.

Hi Curtis, If you want to really manage SLA's and act upon that, JIRA Service Desk would be the most logical answer. Not only does it offer you flexible and JQL-based configuration to set them up, but also everything you need to keep track of them and alert the right people to respond in a timely fashion. It also includes…

Hi Susan, Components are specific to each individual JIRA project. The list of components inside a project is usually not too extensive. If you navigate to the Components list of your project, the Component Lead is shown next to the component lead. If you want to search for issues having a component lead by a specific…

Hi Ashu, You can find all the answers regarding this question on this page: https://www.atlassian.com/licensing/jira-software.html. Regarding the upgrade from 50 to 100 users, take a look at chapter 3 - "What is the cost to upgrade my JIRA Software license to a higher user tier".

Hi Davina, You can raise a support ticket here.

Atlassian has modified the card lay-out, indeed. This change has created some animated discussion. A ticket was created about this here: JSW-15331. Atlassian states: Screen Shot 2016-12-16 at 09.54.16.png So there are no immediate plans to revert the change. Should you have specific remarks or concerns, you can always add…

JIRA Service Desk has this functionality. SLA definitions are JQL-based, so you can perfectly create the kind of conditional service levels you describe. But be aware that it has a lot more than just SLA and that you need to consider setting it up entirely as your IT Support Channel to get all the value out of it. You can…

Hi Manish, This link provides a lot of background on the topic. Seems that you could contact Atlassian support to have it enabled for you.

Yes Manish, I believe it even comes pre-installed on cloud nowadays. See this screenshot from my own Cloud instance: Screen Shot 2016-12-20 at 12.15.11.png

Hi Manish, the field comes with the free JIRA suite utilities add-on.

Hi Manish, As you describe it, I assume the selection of a reviewer is done using a User Picker custom field. If so, you can use this field to limit the transition. Edit your workflow and select the transition you want to limit to the reviewer. Add a condition and select the User is in custom field condition. As condition…

To be perfectly honest, using status to determine if a bug is QA or Dev related feels kind of awkward to me. Ok, a bug may be discovered by QA or while an issue was in Dev, but then I would suspect you create a bug issue which moves through a process (to do > in progress > done). As soon as the bug's status changes, you…

I see the screen shot now. The only thing missing - in my opinion - is how you define QA side and Dev side as a unique piece of information. If you can do that and you replace the 'Assignee' dimension with that piece of information, you will have a report that has the data and click-through functionality you were looking…

Hi Na, For some reason, your screenshot is not showing. So it's kind of difficult to go into more detail about that. Depending on how you have set up your JIRA configuration, I would expect to see multiple lines in your result. If that's not the case, you could add multiple gadgets on your dashboard presenting you more…

Hi, I'm not sure how you determine the difference between Dev Backlog and QA Backlog, but I suppose you might come pretty close already using the two dimensional filter statistics gadget on a dashboard. First, build a JQL filter to collect the bugs you want to report on. Save the filter and make sure to share it with your…

You will need to provide more information if you'd like us to help you on this one: what reports? what figures are you seeing? what numbers do you expect? How is the board configured that holds the reports you are referring to?

Wow, John. Looks like you're actually asking for a full explanation on JIRA Software . There is going some work to do by yourself there! But on the other hand - when you're talking about workflow, you've taken an important step already: you already described your workflow in your question. You can build the workflow you…

Hi Brian, No, that's not what issue level security does. It lets you decide at issue level which issues can be viewed or not, but it does not allow you to add more granular levels.