Walter Buggenhout Community Champion

Hi Pavel, JIRA Software and JIRA Service Desk are two different applications serving different goals. Without going into all the nifty details, both are built on the JIRA platform (which gives you projects, issues, versions, components, workflow and a lot of other common things), but JIRA Software essentially aims at…

Hi Bruce, It is available on Cloud, the release on server has been announced but not released yet. It will come with version 3.3. You can watch the release notes page to stay in the loop as soon as it gets released.

Hi Julien, I am afraid that I will have to disappoint you on that one. The closest you could get to this, would be to make sure you get to the Backlog view of your Portfolio plan (https://your_JIRA_url/jira/secure/PortfolioPlan.jspa?id=20#backlog), but selecting the Epics/Initiative (not to mention specific epics or…

Hi Julien, If you have imported the issue from JIRA, the link is already there. If you have created it in your Portfolio Plan, you can either link it to an existing JIRA issue or create and link a new issue in JIRA. In both cases, the easiest way to do this, is make sure that you can see the issue link field in the backlog…

Hi Sergey, You can't. Cards have been redesigned about two weeks ago. With that change, the position of the issuekey has moved from start to end on the cards. It is not something that can be changed by settings, it's just the new design.

Thx for the heads up and good luck while progressing!

If a scenario like this would generate major concerns for your reporting, a first advice might be simply not to allow tickets to be reopened. And yes, that might imply giving the closure of your tickets' process some thought (e.g. about a pre-closure step in the process, about some form of approval by the customer, ...).…

Hi Manuel, You can go a long way by setting up a template project which holds your default schemes. Then, consider these options: * When you create a new project, at the bottom of the create dialog select "create with shared configuration". You will then get to choose your template project: Screen Shot 2016-12-29 at…

Press g+g on your keyboard and select priorities. Click edit at the priority you'd like to give a new icon. Click select after the Icon URL: Screen Shot 2016-12-26 at 16.27.06.png If you have access to the images url (<your JIRA>/images/icons/priorities/) you could add your icons there. If you don't, you could refer to an…

Hi there, In your project configuration, under screens you will find an issue type screen scheme and one or more screen schemes associated to it. These determine which set of screens is being used in your project for the different available issue types. A screen scheme may contain 3 different screens: * one to create…

Oh, I see. Your problem actually is not so much about how to retrieve the most recent issue and its create date, but about the permissions. In order to find issues in a certain project, you need to have access to it. More specifically the 'Browse Project' permission. As JIRA Administrator, you are usually the one who is…

Hi Jashir, You can create a JQL query that looks something like this: Project = <my project> ORDER BY created DESC This will give you a list of all issues in the project, having the last created issue on top. In issue navigator, display the created column in your search results and you have your answer. If you want to take…

Hi James, No. A swimlane is a horizontal lane in your board you can use to group issues by. If you want to get some more background, take a look at e.g. this page.

Hi Diane, Throughout a year Atlassian releases multiple new versions of its software. For JIRA Software alone, 7 releases were out between August 23rd and December 7th of 2016. At a rate like that, printed media are not the best way to get documentation to people. There are, however, quite a few books out there. I stumbled…

Hi Jelle, the permissions above seem right. Atlassian also explicitly states that you should use the Service Desk Customer - Portal Access security type to grant permissions in the permission scheme and not the Service Desk customers. There is one more thing that comes to my mind. Inside your Service Desk, you also have…

Hi Jelle. I don't think that you should change your permission scheme but have a look at who is in the Service Desk Customers role in your Service Desk project. It is the people having this role that can actually access your service desk through the portal. 

Hi Jelle, Customers can only see the Service Desks they have permissions on. This could be because they have 'browse project' permission on the Service Desk project or because they are added to the Service Desk Customers role of certain Service Desks they actually shouldn't see. An easy way to check the permissions of a…

The documentation you refer to describes how you set up application access and linking for unknown users. If you want known users to use it, application linking between JIRA and Confluence get you to the same point. To make your knowledge base accessible for the Service Desk, go to the project settings of your Service Desk…

You're welcome!

No problem. What version are you on? I tested this on Cloud and JIRA 7.2 server. In both cases I can move multiple issues at once. I go about like this: * Select 1 issue * Select additional issues (holding ctrl or cmd on mac) * Drag to a different location (a red number pops up showing how many issues are going to be…

You got me a bit confused as you mention the backlog but tag your question as jira-core. If you really talk about the backlog view of a scrum board in JIRA Software, you can move the batch with drag and drop.

Hi Aileen, Just to clarify: is it a kanban board or a scrum board (are you using sprints or not). And what is the JQL behind the board?

The version report refers to the fix version.

Hi Tom, I'd advise you to talk to an Atlassian Partner or - given you're on a Data Center path - your TAM from Atlassian for some guidance around this. From my experience, if you take your questions to the table and invest a couple of hours to max 1 or 2 days, you should have all of this cleared out for you and maybe even…

Sure. SLA configuration is based on JQL filters. So if you can somehow filter your issues per customer, you can set an SLA per customer.

Hi Emily, I want to avoid to go into a discussion of what might be 'Agile' or not, but focus on the more formal concept of releases and sprints. Something I have been doing on several occasions, is use a time based concept as releases. This may be useful in a consultancy or any other environment where you rather have time…

Did you: * associate the account field with the JIRA projects? * add the account custom field to the field configuration and screens of you project? * make sure the account is filled out on all the issues within your projects? As your users are booking time against issues, the account must be associated with your issues…

Hi Jack, The team information is indeed managed by Portfolio, but stored in a separate area outside Portfolio. Since the release of Portfolio 2.1.0 (October 7th), the Team field has been made available in JIRA Software as well: 2016-11-20_121413.png See the release notes for more information and scroll to version 2.1.0 to…

Hi Susanne, Tempo books is no longer available as a separate product. Books features have been incorporated in Tempo Timesheets as of Timesheets 8.0. That's probably why you only see Timesheets in your list of installed add-ons. For a little bit more background, see this…

Hi Raul, Portfolio 2.0 (with live plans) has gone live in May this year. So it is definitely in production!