Walter Buggenhout Community Champion

Hi Jimmy, I'm afraid you lost me there. I think everything is here for you to solve your problem. From what you are describing, my guess is that you are trying to link existing stories to epics from the list of epics in your Portfolio Plan. That is something you cannot do. If you want to link existing issues (tasks,…

Ok. If you switch your scope to Epic view like this: Screen Shot 2016-11-07 at 15.31.34.png Do you see the indication of issues without parent epic at the bottom of your Epic list? Screen Shot 2016-11-07 at 15.31.52.png And while you are checking that ... are all your epics from your project visible in that same list?

Some things you might look at too, if you can't immediately relate to the source of your Plan: Screen Shot 2016-11-07 at 14.38.44.png

Hey Jimmy, What is the source of your Portfolio 2.0 plan? Is it a Project, a Board or a Filter? If your existing JIRA issues are part of the source of your Portfolio plan, there is nothing you should do specifically in order to get them in your plan apart maybe from refreshing your screen.

Hi Jimmy, There's 2 ways to do this (assuming that the plan you created is a Portfolio 2.0 plan): * either just link the existing features and stories to your JIRA Epics directly. This will reflect automatically into your Portfolio Plan * or in your Portfolio plan, make sure you scope view is set to display issues at Story…

Hi William, The colors are just a visual aid that you can use to give any meaning you would like to assign to them. Suppose you have epics from 4 different business areas on the same board, you can categorize them like that. We use them to differentiate between internal project, consultancy for customers and business…

Hi Emily, On the right side of your screen, there is a separate section showing all date fields. Have you checked if the Start date isn't over there? Screen Shot 2016-11-22 at 16.13.36.png

Hi Lior, Unfortunately, you cannot expose your beautifully crafted Dashboard through the Customer Portal. The dashboarding functionality is part of JIRA Software and JIRA Core, but not of JIRA Service Desk. To have some insight on the status of tickets, your Service Desk users can have a look at the 'Requests' page (from…

It should be on the left of your screen, given you are on a scrum board: Screen Shot 2017-02-22 at 19.41.46.png If your board is a kanban board, you won't see it as kanban does not use sprints. In that case, you just select the kanban board from the side panel.

Hi David, Go to Site Administration. In the Billing section you will find an entry "Manage Applications". From there you can deactivate JIRA Service Desk or click through to your agents and revoke agent access. Screen Shot 2016-10-07 at 10.47.52.png

You could also give each user an issue with an original estimate of 15 days to book personal vacation against. Your remaining estimate is what is left for that user.

Hi, It seems like the update just happens automagically, but you have control over this yourself. The update is being triggered by a post function on the transition that is applied to close your story/sub-story. If you want the same thing to take place for Change Requests, first have a look at the workflow that is…

Nice description of your case! Nevertheless, it will always be difficult to give proper, well founded advise on this with only a small one pager. Just a few points on your questions: * Don't ever assume anything . But from what you are saying, having a single project representing the e-commerce website seems to make…

Hi Joshua, First of all, you need to create a Comment Screen if there isn't any in your JIRA instance yet. I suppose this is what is causing your problem. In the admin section of JIRA, go to Screens and add a new screen. Name it "Comment Screen" and don't add any fields to it, like this: Screen Shot 2016-10-01 at…

Epics are a specific issue type that have this create issue in epic feature. It comes with JIRA Software and adds e.g. the ability to filter your backlog by them on a scrum board. Standard issue types - such as initiatives - do not have this feature. When using JIRA out of the box, you can use issue linking to reproduce…

Indeed. This is intended behaviour, as you should not change your original estimate anymore once you started work on an issue. Changing your original estimate automatically makes it not your original estimate anymore, but an updated estimate. So once you started, only update your remaining estimate. If you spend more time…

Hi, Portfolio for JIRA is a JIRA add-on following standard Atlassian pricing. This does not have anything to do with administrators, users or viewers, but with the user tier of your JIRA application. As explained on the Marketplace add-on page, the add-on tier is set automatically based on the maximum tier of the licensed…

Hi Emma, Judging by the tags on the question, I'm guessing your question is related to JIRA Service Desk and SLA targets. If not, this answer will be quite off-topic . In your Service Desk project, go to Project Settings and select SLAs. If you look at any SLA (Time to first response in the screenshot example below),…

Hi Joseph, No, in JIRA you always log hours on an issue. A common approach to allow people to log their work of a "more general nature" is creating an issue specifically for more generic work and having people book on that issue. Then, of course, if you want to get an overview of logged work across projects, Tempo…

You're not going crazy This is brand new functionality to actually split an issue in 2. Screen Shot 2016-12-28 at 14.03.15.png It is intended to split up a larger story into smaller chunks, which you could add to different sprints. The nice thing about it, is that it copies all relevant information from your original story…

Shared reports have indeed been released with Portfolio 2.1.0 (October 7th). See the release notes over here.

Hi Christoph, The prediction does not assume there is no work associated with the unestimated issues, but as there is no estimate, it cannot take them into account for the prediction. There is some information that might help you interpret the accuracy of the report: A first thing - as also mentioned in the documentation…

Hi Mark, When you assign an issue to a sprint, you actually fill out the value representing the sprint in the Sprint custom field. If you want to be able to modify or remove the sprint easily, you can add the Sprint custom field to the view and edit screens that you are using for your project(s). From then onwards, you can…

Hi Frode, Not really, but you might work around this. In the side bar of your project, there is an option to include links to any useful resource that has a URL: Project Shortcut.png Just click 'Add shortcut', paste in the URL to your dashboard and call the link 'Project Dashboard' (or any other fancy name you'd like to…

JIRA Service Desk comes with 2 out of the box reports for this: * Article usage (number of article views and problems solved by articles) * Article effectiveness (problems solved by articles and requests created) Screen Shot 2016-12-17 at 14.57.17.png

Hi, You can do this through bulk change, but you will most likely run into the problem that resolving issues requires a resolution and the resolve issue transition has a screen defined for it. Do not change that transition. But edit your workflow and add a transition bulk resolve to it. Make sure that you do not associate…

The fields you are adding will be JIRA fields. They will be added just as they are configured in JIRA. For you specific example, if you add the Priority field from JIRA to your form, it will be populated with the options you already have available in JIRA. If you need other fields, you can select or configure them from/as…

Request forms in JIRA Service Desk are set up as Request Types. Go to the project settings of your Service Desk project and select Request Types. Over there, you can associate a new Request Type with an underlying issue type, select an icon, title and description for your form, configure fields and so on. For more info on…

Agree with Nic. Or if it's just for yourself, hold the cmd button (on mac) or ctrl (on windows) while you click. The link will open in a new browser tab then.

Hi Steen, "Merging" tickets is not really possible. The usual way of solving this would be to decide which ticket will be your main ticket, link the other ones to it (with a link type duplicates), close the duplicate tickets and maybe indicate 'Duplicate' as a resolution. If you are talking JIRA Service Desk, this will…