Walter Buggenhout Community Champion

Hi Laura, I started using the Epic Sum Up add-on for this about a year ago. Simple to set up and very easy to use. You can find it in the Marketplace right here: https://marketplace.atlassian.com/plugins/aptis.plugins.epicSumUp/cloud/overview The PRO version is commercial, but there's also a free version that has the key…

Hi Alex, Yes, it should be in the People section. If it is not there, take a look at the screen configuration of your Service Desk project: * Select your project * Go to Project Settings * Select Screens * Select the screen associated with the view issue operation If you don't see the Organizations field, add it to the…

This is possible as from Portfolio 2.1 through a parent-child link. How it's done is described on this page, but as I just mentioned, it requires you to be on Portfolio 2.1 or later.

Hi James, No, it doesn't work that way. Your transitions are part of workflows. There you have statuses and every step you can take from one status to another is a transition. On each workflow transition, you can - optionally - configure a transition screen. The screen allows your users to add additional information during…

Italian language packs are available at translations.atlassian.com. This link brings you the download page for bitbucket, but you can select JIRA and other products as well. Installation instructions are on the referenced page.

Hi Bart, You can perfectly link Confluence pages to JIRA issues. The same way you link JIRA issues to each other, just select More / Link and select 'Confluence Page'. You can paste the URL or search for a page through some filter options. The link to the Confluence page appears under Issue Links once you're done. With…

A sprint goal field is available on Cloud, but - indeed - not on server yet. See my answer to your other question around this topic here: Sprint Title is limited character field (~30 characters only), which is not enough if Sprint Goal is also required to be included in the field. So one specific field for capturing the…

Hi Ammar, Your observation is correct. There is indeed no direct way to associate a story to an initiative. As a workaround, you could of course create a generic umbrella epic linked to each relevant initiative to account for ad hoc issues. 

Hi Remington, I guess this page should get you started. I believe this is the how-to you are referring to.

You can do exactly what you describe in backlog view. The top sprint in the list is the active sprint. If you right click an issue there, you can get it to another sprint or to top or bottom of the backlog. Drag and drop is an option to in that view.

Hi @Dion Park, I can understand your point. Just implementing the log work field and not making it required doesn't cost you anything.

I second Alex on his point that not in all cases a work log might be required. That's what I meant when I said you should verify whether you can really enforce 'to make a worklog required when resolving an issue'. I would personally be careful too before you make logging work required. But that's an assessment you have to…

Resolving an issue means you are executing a workflow transition. In this transition, you should already get a screen with the Resolution field on it, which I would expect to be required just as well. Check your workflow to see what screen is being used on that transition. Just add the Log Work field to that screen: Screen…

Hi Christien, In JIRA Software you would add the same information on a Dashboard. A Dashboard may be specific to a single project, but it might just span multiple projects as well. The gadget you would want to use to display Activity with is called the Activity Stream gadget. And it does the same thing as the default…

Hi Tomas, Good and rightful point. It is possible to create a project based on the configuration of another project. When you choose to create a new project, select "create with shared configuration" in the dialog. You will be able to select another project to copy the schemes from: Screen Shot 2016-12-15 at 09.43.58.png…

Hi Helen, You can add users to JIRA Software and use the permission scheme of your projects to make them look as if they were read only. That's just a matter of granting the right permissions to your customers on that specific project. For a detailed listing of permissions, see this page. To answer your licensing question:…

By clicking the "+" icon, you are actually adding a sub-task to the selected story. I suppose that you don't have a sub-task issue type in the issue type scheme of your underlying project, hence the error. To add a story, scroll to the bottom of you Story backlog in Portfolio and click the Screen Shot 2016-12-29 at…

Hi there, Although formatting there is not exactly WYSIWYG, you can apply markup to do some key formatting. A few tips to help you started: * for bold type a * before and after your text. * for italic type an _ before and after your text * for underlined type a + before and after your text * use square brackets for…

Hey Kevin, That sounds a bit strange to me. Your setup might be influenced by whether you are on Cloud or Server and integrate with an external user directory (such as AD) or not. Steps you can take are: * Go to User Management on your JIRA instance and select Groups * Add a group 'Premium Support' * Add members to this…

Hi Kevin, You should not modify the permission scheme to control access to your Service Desk project. The Portal Access is what makes your customer have access to the specific Service Desk portal rather than the internal JIRA project behind the scenes. Make sure that your customers are assigned to the Service Desk…

You should add the estimates on Story level, not on the subtasks.

Hi Davina, You have selected the "assignee" field as a required field. On your issue transition screen, you are using the "assign user" field. Those are two different fields and the "assignee" is not filled out in your screenshot. That's why JIRA is showing you the message.

You can't do this with out of the box functionality in JIRA. There's add-ons that support you to do this with advanced functions, like scriptrunner. If you have that on your instance, have a look at this page and look for the function IssuesInEpics.

Cool 

I think this is an interesting discussion . Note that the Schedule Issues permission is a Board permission. So it relates essentially to being able to drag issues into a sprint in the backlog of your scrum board. In Niall's question, we are at issue creation. So there is no board in play yet. Given the permission would…

Hey @Ignacio Pulgar, no offense and just trying to help. I see that it's there, but maybe that's an error in the docs. Here is more info on Scheduling issues specifically (also from the docs). 

Sorry to jump into the discussion here, but I am not expecting this to work. The Manage Sprints permission allows you to control these actions: * Creating sprints * Starting sprints * Completing sprints * Reopening sprints * Reordering future sprints * Deleting future sprints * Editing sprint information (sprint name and…

Hi Niall, Indeed. The Schedule Issues permission @Ignacio Pulgar is referring to, relates to the Due Date field, not the sprint. The first and most logical option - in my opinion - would be to use JIRA Service Desk as a service desk. It is designed specifically for that purpose. In there, you design the screens for your…

Hi Richard, That's strange. I should expect you would go to the Atlassian Marketplace, locate Table Grid Editor over there and simply click the Try it free button at the right top of your screen. Then you should be taken to a screen on your my.atlassian.com account where you should be able to generate a license key. (Make…

The part about the licensing is true. But you could take a look at the Control Chart report (this already gives you some insight in lead times on your issues). You could also search the Atlassian Marketplace for some SLA specific add-ons.