Walter Buggenhout Community Champion

If you are using Tempo, you could use the Timesheet Report. Build a JQL filter to fetch all the issues related to your epic ("Epic Link" = [key of your Epic]). Save the filter and use it as the source for your Timesheet Report. This approach might be slightly unpractical, as it will require you to leave the context of your…

Sneak peak ... On cloud a big redesign is coming. You might have a look at the keynote from last week's Summit: https://community.atlassian.com/t5/custom/page/page-id/summit-europe-2017 The redesign part can be found as from about 1:05:00 in the recording.

Hi Ahmed, A quick way to help you take the right decision might be this: if your new app has its own components or a separate versioning, create a separate project. Both versions and components are project specific, so you should manage them in separate projects. If that's not the case, your application might also become a…

Hi Martin, Building reports by agent is not too difficult. The below screenshot is from a default report "Incidents by priority": To do the same for agents, just select an agent in the Filter By section. Add a series for each agent. The hard part is when you would like to combine Incidents, Service Requests and other…

Hi Rashmi, I am not entirely clear what your question really is. To make someone an agent, that person needs to be granted Application Access to JIRA Service Desk. That is a function only available to JIRA (System) Administrators, mostly done by adding the person the the service-desk-users group in user management. So that…

Devon Henderson wrote an article about filtering boards (and across boards). There's tips in there that might help you find cross-board cards at least. Prioritising them cross-board is another pair of sleeves, as people might say in my mother tongue. Just on a side note, as a software developer, I think JIRA Software might…

Hi Stephane, Yes, you will have to release your releases individually from within JIRA. This release process is quite complex and includes checks and wizards to decide what needs to be done with unfinished issues assigned to a release at time of closure. That issues can still be added to a release is related to the release…

Hi, Refunds can be requested until 30 days after you purchase. After that, there are no refunds anymore. See this excerpt from the licensing FAQ: If you want to co-term your licenses, contact an Solutions Partner. This can be done at renewal or purchase of new licenses, but the maintenance period of at least one of your…

You could try something like: assignee was currentuser() AFTER 2017-05-01 and assignee was currentuser() BEFORE 2017-05-10 It will still give you issues that had the Current User as assignee outside that date range if they had been assigned to that user previously. So you might further refine based on other criteria as you…

Hi Bart, I sent you a 1-1 message on this.

Hi Amol, Technically this would definitely be possible. I'm sure you don't want to implement a procedure like this from a process/business perspective. If you want to follow up on certain issues, just put a value in the due date field, create a JQL filter showing the issues with a due date today or e.g. coming up in the…

Hi Jason, The burn-down chart is just a report. It just reflects what you do. So indeed, if you change estimates on issues already in your sprint, this is reflected in the chart as an increase in story points. Simply because that's what it is. I would not call this restrictive. There is nothing that blocks you to add or…

Hi Erica, The 'Business' option under Projects is a type of project. Just like a Software Project, it is a container for issues. It automatically comes with a board specifically for it. This board, however, offers different (and a bit less) functionality than a scrum or a kanban board for Software use. It contains only…

You might be able to get this done with the Extension for JIRA Service Desk add-on. It offers the possibility to calculate an SLA based on a date (such as due date) and it allows you to show the SLA timer on the customer portal. The add-on is commercial. So if you are looking for a workaround, you can always mention the…

Hi Jeff, This might be a permission issue. In order to see issues from any project, a user should have 'Browse Project' permission on that project. When you say 'users have switched projects', it's important to check they still have this permission on the project they came from. Otherwise they will no longer be able to see…

Hi, The shared configuration consists of the configuration schemes. As the custom field context is not part of a scheme that you associate with a project, this is not automatically adjusted. There are use cases where it might seem as if the context is taken into account. Suppose you show the custom field on issue type…

Hi, There is a long standing suggestion to implement this, but as of now this is not possible. If you want to stay informed of any changes, you can always track the suggestion over here: JRASERVER-17783.

Maybe an unconventional suggestion, but it almost seems as if someone just changed the background and text colors of the portal header to white, so it doesn't show anymore. Navigate to your project settings, then select Portal Settings on the left and click View and customize the look and feel of your Help Center. Then, as…

Can you access the overview page directly through its url? That would be something like https://yourdomain.atlassian.net/servicedesk/customer/user/requests?status=open

Although you do not mention what the workflow behind your story is, I think we can safely assume that a story is only closed when all work on that story is truly completed. As a consequence, you do not reopen a story. There may be good reasons that additional work is required. Maybe a bug has been discovered. In that case…

When they log in to the customer portal, they should see a link in the top right corner called 'Requests'. From that link, they should be able to see the link. If not, could you share a screenshot from a customer view?

Hi Cindy, That's a very open question. There's a lot of questions one can ask in return. However, I guess the baseline would be to measure and adjust accordingly. A good starting point might be the Velocity Chart (See documentation over here). It will compare your commitment to your actual performance. And it will keep…

Hi Matt, The behaviour you see is typically wiki style. *bold* represents the bold styling in wiki markup. Since JIRA server 7.2, Atlassian released a WYSIWYG editor, but this is not available on Cloud (yet). See also the comments on this issue: https://jira.atlassian.com/browse/JRASERVER-8943

If you just want to change the fields' order on the screen, go to your Service Desk project (Resiflex) and then go to Project Settings (on the bottom left of your screen, possibly represented by a cog icon). Then select Request types and locate the "Report a system problem" request type. Over there, click "Edit fields".…

I hope this extract from the documentation answers your question: What the 'estimate' represents, depends on the estimation statistic you chose for your Portfolio Plan. If you selected time based estimates, this will be based on the original estimates field, if you selected story points, it will rather be the story…

Hi, As Portfolio focuses on planning ahead (and thus remaining work), its scope filter by default excludes completed issues from the view. This is something you can fix by setting the status filter to Open and Completed issues. For a bit more background, see scope filters documentation.

It is very well possible that Thomas' answer is what you need. However, it might be easier to assist if you could just specify exactly what you need, rather than using D / E / F to represent what you call 'the worklows'. A workflow consists of statuses (created / in progress / done in your example) and transitions (the…

You will need administrator access for this. Resolutions are under the administrative options. The quickest way to access them is to type gg on your keyboard. A dialog will pop up in which you can simply type Resolutions. Selecting the option will directly take you there. Or you could select the cog icon in the top right…

Sure! Using JQL you can create dynamic filters that can help you do this. A few suggestions to filter for recently created issues might be: * created > StartOfDay() (issues created since the start of this day) * created > StartOfWeek() (issues created since the start of this week) * created > StartOfMonth() (issues created…

Hi Vivian, you are looking at the documentation of Portfolio Classic Plans, which has been replaced by live plans. Classic plans have been discontinued in Cloud since March 31st 2017. Live plans does not have the same configuration settings anymore. You can find some background on progress tracking on this page.