Walter Buggenhout Community Champion

Hi @Karl Kalantari, If your resolution is being set automatically, this is because it is being done through a post function in your workflow. If you investigate the transition where your bug is being resolved, you will find a line stating something like "Set resolution to Fixed". If you want to be able to set the…

Apparently this feature was introduced in Jira 7.6. There is a report on this that you can find here: JRASERVER-66473. In the referenced issue, a workaround is described to disable the feature by means of a dark feature. It may have an undesirable impact however on how subtasks can be sorted on issue detail view of their…

Hi @Chamilka Baranasuriya, No, there isn't. This is a very specific permissions setting you are referring to and it is not keyboard enabled as far as I know. For a list of available keyboard shortcuts in Jira, pressing the ? on your keyboard. A dialog with the list will pop up.

Hi @Thivanka De Silva, You could come really close with a two dimensional filter statistics gadget on a dashboard. First, create a filter to collect all the issues you wish to report on and save it. Then, add the two dimensional filter statistics gadget on a Jira Dashboard and use the filter as the data source for the…

Oops, sorry @Karl Kalantari. My bad. I updated the link. It should be fine now!

Hi @Karl Kalantari, You are asking about one of the key concepts of Jira here: its powerful workflow engine. To unleash the potential of this very powerful tool, it is crucial that you understand this key concept. Please have a look at the documentation on Working with Workflows. Everything you need is in there: setting…

I can understand your frustration, @[deleted], As I have no insight in your settings regarding team capacity etc, I quickly set up a trial plan for myself where the timeline was immediately showing what you are expecting to see. As I cannot see some of your settings from your description / screenshot, can you just verify 2…

Hi Sharon, What we do is use story point estimation for stories, but not on any other issue types. So bugs, tasks and spikes are estimated with the Original Estimate field (in hours) whereas we use story point estimations for feature development (stories, as I already said)

Hi @Alec Spyrou, Team calendars - unfortunately - is functionality in Confluence, not Jira. It is capable of displaying Jira issues based on dates, but as an add-on to Confluence.

Hi @Luciana Di Matteo, As @Alexey Matveev is saying: for linked issues, this is not possible out of the box. The Atlassian Marketplace does offer quite a few apps (add-ons) that may help you solve your issue.

Hi @[deleted], From what I can see, the chart is correct. Maybe there's a few misunderstandings, so I will just try to explain why it looks the way it looks. One thing to note upfront though: although the chart shows coloured bars to represent work items, it is not a gantt chart. It is a graphical representation of your…

There's two things I can think of. Either your JSD project is not using the normal permission scheme for Service Desk projects. Or - and I think this is the most likely option - because your Jira instances are hosted on different servers, they are simply 2 different Jira instances. Which makes your Service Desk instance is…

Hi @Ashish Yadav, Just a couple of things I can think of: * Based on your response: could you make sure you are searching for a program? If you are searching for the issues in a Plan, you should use "issuekey in issuesInPlan(18)" instead of "issuekey in issuesInProgram(18)". * Also the "issuekey in" part should be there. *…

Ehm ... now you have me confused. Jira Server (2.13) should have the JQL function just like that. But in Jira Cloud it is unfortunately not available. See reference documentation here: * Portfolio for Jira Cloud * Portfolio for Jira Server 2.13

Hi @Ashish Yadav, Could you check the version of Portfolio for Jira you are using? And also; are you on Server or Cloud?

Hi @JIRA DNBCB, You should add the user to the Service Desk Team role instead.

You're welcome. If you have EazyBI in place already, this should be walk in the park :-). If the answer helped you out, could I ask you to accept it? That way it becomes easier to find for users with similar questions in the future. Thx!

Hi @Richard Minerich, Yes you can. In the configuration of your plan, you decide which estimation method to use for your plan: As you can see from the screenshot, planning units are Days / Hours or story points. you can find the setting by clicking the 3 dots [ ... ] next to your plan's name. This will bring you to the…

As of Portfolio for Jira 2.11 you can search for all issues in a plan or a program like this: All issues in a Portfolio Plan issuekey in issuesInPlan(54) where the number '54' is the unique id of your portfolio plan. The ID is shown in the url of your plan. All issues in a Portfolio Program issuekey in issuesInProgram(30)…

Hi @Radosveta Delcheva, You will need to combine a couple of things here. The SLA you configure is configured for individual tickets. So, for the first part of your equation, just configure a Time to Resolution SLA of 90 minutes. Each ticket resolved within 90 minutes will be considered as resolved within SLA; any other…

Hi @Andrew Whelan, Assigning a team to a board in Portfolio does not make it impossible for a single member of a shared team to be assigned to issues from different JIRA projects / boards. If you want to assign a team member from a different team to an issue, you will have to change the team responsible for that specific…

Hi @Kavitha Kandula, You are asking a process question here and answers to those can be very long. I will try to keep it to the point and give you some food for thought. From the description of your process, it seems that you consider your story to be done once it is deployed. Or maybe when it is ready to be deployed, but…

Hi @viraf, Wouldn't the easiest option be to set the product in a custom field or Component/s when you create the ticket from your e-mail alias and then use that field for easily defining your queues per product?

Hi @viraf, the feature is not available on Jira Cloud yet. There is an open feature request for it that you can watch / vote on to stay informed: JSDCLOUD-631.

Hi jyostna.pokala@cigniti.com, Your first query is powered by the Scriptrunner app from Adaptavist (see the issuefunction in ... part - that is not standard Jira functionality). The watcher query does not use the Scriptrunner app. So as the error message says, check with your Jira Admin if he can fix the license issue.…

Hi @Kavitha, The assignee of the ticket is the person who owns the ticket at the current moment. So if your team member is the one reviewing, he should be the assignee during the In review status. If the result of the review should be that the task is marked as Done, it makes perfect sense that the reviewer is the one to…

Hi @Sathish T, Just my 2 cents: * for the use case as you describe it, have a look at this marketplace app and see how far it can get you. * or maybe more radical: consider Jira Service Desk to collaborate/communicate with your customers around issue tracking. The Service Desk interface does not expose any internal…

Hi @LaryPeters, Unchecking the active checkbox deactivates the user. From the Atlassian documentation, deactivating a user has the following effects: If you remove a user from the Jira users group, you effectively remove all permissions associated with that group. Unless the user belongs to any other groups that have…

Hi @Sathish T, As far as I know, hiding time tracking is not an out of the box feature in Jira. If you are using the Hide time tracking for Jira Cloud app for this, the visibility of work logs is controlled by the Work on issues permission. So, if my guess is right about your implementation, make sure your customers don't…

Hi @Larissa D James, You can find documentation here: * for the Server version * for the Cloud version Interesting as well is to have a look at best practices regarding portal setup. Those are important as what the user sees depends largely on how you set it up. There is literally just a couple of different screens: the…