Walter Buggenhout Community Champion

Hi @Jaye Wong, Did you try through this page?

Hi @Jill Guardanapo, "priority" (as determined by the priority field in Jira) is not a factor that impacts the scheduling. You may be confused by the issue's order in the backlog instead. Roughly, the scheduling behaviour is based on the following: * Issue rank in the backlog (at story level) * Available capacity (and thus…

Or just right click the issue card on a board and click 'Add flag'.

Hi @Sam Wilkinson, A scrum board by default has all the issues in the backlog as long as they are not added to a sprint yet and the sprint they are in has not been started yet. While you can have only one active sprint on a board, you can create more in the backlog view to help you organize / prioritize your backlog in a…

Hi @Sébastien Antoniotti, You are looking at the name of the Agile board associated with the Projet test sur Jira. Renaming the board itself should change what you see there. To do so, just click the link PTSJTableau de. it wil take you to the board itself. Then, click the button with the 3 ... at the top right of the…

In the users list of your Service Desk project, select the organization so you can see the users in it. Then, at the top right corner of your screen select the option "Delete organization":

Hi @James Foley, This is not available out of the box. Through the Atlassian Marketplace, you might find apps that help you enable this, like Intenso's Extension for Jira Service Desk (only available for Server). If you are really confident about your service levels or want to inform your users, you can use an Automation…

Hi @Olivier Desilets, You've done the best you could with this gadget. The current month will always be displayed, with zero values if you exclude this month's data. You can create a similar chart with the Recently created chart. It has the same problem, but as it uses bars instead of lines, it shows nicer on a dashboard…

@Jack Brickey, @Rich Ireland, I tried too and this works indeed. The issue is related to the new UI Atlassian is rolling out on Cloud: Boards in the new Jira experience.

Hi @Rich Ireland, The screen you are seeing IS your Jira Core (Business) Board. Normally, you should see your issues there by default, no configuration required at all. The configuration of the project itself has something in it that prevents your issues from being shown on the board. You cannot configure your board in a…

Ok, You actually are at the board. Some of the reasons why you don't see your issues are these: Read more here and have a look at your project configuration.

Correct, You cannot create a board yourself for a business project. If you just select your business project from the projects list, what is your default project view? The screenshot I added above shows where you should find the board from the side bar. In the old layout it should look like this: If you really want a full…

That's not right, @Rich Ireland, A business project (Jira Core) does have a default board out of the box, that gets created with the project and just reflects the project's workflow: You cannot edit it though, it does not have a backlog view and so on. If you say a business project does not have a board, how do you define…

Business projects have their own, out of the box board with somewhat more limited functionality. Scrum and Kanban boards are a feature specific of Jira Software and indeed can only be built on Software projects.

Hi @dineshsp, You could search for any definition online and I could try to give you one, but that would not make any sense. Jira just offers you a list of 5 priority names to manage prioritisation of your bugs or incidents. Blocker would be the highest level of priority and trivial would be the lowest. The others rank in…

Hi @dineshsp, They are (just) default names for level 1 / 2 / 3 / 4 / 5. If you want them named otherwise, you can do so if you are a Jira Administrator. The only thing to keep in mind, is that you are changing them for your entire instance (for now that is; in the very near future, you will be able to set different…

Clicking through on the issue count will show you the list.

Hi @David D Bigness Jr, The screenshot is from an old presentation at Atlassian Summit 2015, which announced the big upcoming change to what is now Portfolio 2.x with live plans. After the presentation, it has taken many months before the product was released in its current form, with full integration into Jira (which was…

Hi @Jessie, As far as I know, you cannot save this report. However, if you are open to other solutions to achieve a similar result, you could use the Two Dimensional Issue Statistics gadget on a dashboard. It is also based on a JQL filter and allows you to show the count of issues in 2 dimensions, in your case: team and…

Allright, @David Jessop; great! If the answer helped you along, would you mind also accepting it on the Community? That would help other users with a similar question find it more easily in the future. Thx for the feedback!

So each team can track its own report. Do you have different versions per team because teams work across different Jira projects in one board? Or is their a different reason for that (my last question to understand your situation, I think)?

Hi @Jens Niedrich, Thx for the additional input! I think it still comes down to the goal you are after: do you want a traceable SLA that helps you solve issues on time (i.e. within preset SLA targets) or do you only want to report on lead times (for informational purposes). In the first case, I would recommend you to…

Hi @Jens Niedrich, I may be misinterpreting your question, but you seem to be saying that you create Service Desk tickets before incidents actually happen ("creation date is older than the event of the incident"). I assume that it is probably the other way around and that you run into a situation where tickets are created…

If you are using a single board, how do you define your different teams? 

Click the magnifying glass in the side bar on the left and from the menu that opens up, choose view all issues. This brings you to the issue navigator. You can also click 'issues' in the same sidebar and then select 'Search issues' from the menu that pops up. Or even quicker, using keyboar shortcuts: press 'g' and then 'i'.

Hi @Manikandan K, As you appear to be running a scrum board, have you considered looking at the default Jira reports for that purpose: - the Release Burndown Report - the Epic Burndown report (the same, but focused on a specific epic) - the Version report (which is slightly different, but forecasts your end date)

Hi @David Jessop, The 'duration' you mention would usually be set using the Original Estimate field, which you can add to your projects/screens as the Time Tracking field (it is called like that because you also get the remaining estimate field with it, as well as the option to log work). Users require Work on Issues…

Hi @Nico Paffen, Definitely. In your Portfolio plan, make sure you import both your initiatives (use the project as issue source) and the rest of your backlog (preferably use a board as your issue source). Filter your scope view to Epic level and make the Initiative column visible. Then simply map your Epics to the…

Hi @Muhammad Marhoon, I understand what you are saying. You also mentioned that a task shows up when you create an issue at story level, so I wanted you to check first what issue types you have mapped to each hierarchy level in Portfolio. One more thing you could check, is which issue type scheme(s) is/are being used in…

Hi @Brian Milner, This is a really much discussed topic. A good thread to check out might be this one, where a lot is explained about why this is the way it is, arguments representing opinions for and against, links to additional information and even the odd suggestion for a workaround.