Walter Buggenhout Community Champion

Hi @Stefan Kobitsch-Meyer and welcome to the Community! If the permissions across your site have been configured properly, granting access to an external user is exactly the same as to an internal user: * The user needs product access, as viewing data from a Jira project (even through a Plan) requires a license. * The user…

Hi @Brian Ventura, There should be no impact whatsoever on the features of your project. An evaluation license key does exactly the same as a purchased license key: it grants you the permission to use the product. All it does differently is expire sooner. Hope this helps! 

Hi @Ethan Walker and welcome to the Community! Are you sure your question is about Atlas? Atlas (which is now being incorporated in Atlassian Platform Experiences and is no longer available as a separate product) works with projects and goals, but not issues or tickets. With these Atlas projects and goals, notification…

Hi @Andrei Eleodor Sirbu, Unless you explicitly record this somewhere - as you are currently doing - I can't think of a way to do this immediately. At the same time, why would you want to do this? Capacity is typically something useful when you are planning ahead. The data you get from story points resolved gives you the…

Hi @Henry Chad Apale and welcome to the Community! I have no solution for what you're trying to do, but an attempt to clarify why issues with a running state are not included in the metrics. Simply put: the calculated average you would get in your report would be outdated the second you pull the report. Jira stores time in…

When you use sprints, these are designed to select work that yo will be working on for (typically) the next two weeks. That may be a different period, but it should be a short iteration. At the end of that period, you should close your sprint. All issues that are at that point in the rightmost column of the board,…

Well, indeed. That is a consequence of applying different (business) rules in different places. Depending on how many projects you may have in place, you might consider setting up similar automation rules in each project. Or you might add a condition to the global automation rule (Field Value > Project is not one of > list…

Hi @Eliot Hong and welcome to the Community! While I cannot imagine why you would want to set up a process like this (having a status to mark issues for permanent deletion, deleting issues altogether, in your current setup even Done issues, ...), but that would be an extensive, different discussion ... After your sprint…

Hi @Tanuj Kukreti and welcome to the Community! I am not sure what you are trying to achieve. If you want to remove a board view (or another view) from a JPD project, you can click on the ... menu that appears when you point at the view and then select delete to remove it: Hope this helps!

Hi @JK, That is correct. If you work in sprints, all issues assigned to a sprint will be displayed for the full length of that sprint on the timeline. This is how it works by design. There is also a difference between your estimate (i.e. the amount of work something is going to take for completion) and the duration of the…

Hi @rishi raj and welcome to the Community! You started with 18 SP, then you added 3 SP and reduced 2 SP in total. So you currently have 19 SP in your sprint, which is 1 more than the 18 you started with. A difference of 1 compared to the original 18 equals 1 / 19 or 5.5555 % (which the gadgets rounds up to 6%). Hope this…

Hi @Monika Rani, That request needs you to aggregate a lot of data and then calculating averages on them. I would definitely recommend you to look at a BI reporting solution. You may have one available in your company, but if you don't, you might want to look at EazyBI for this: I built the above on report quickly,…

Hi @Jens Prokoph, I don't think I fully understand what you are asking for. From what you describe, it looks as if you have an automation rule working on your JSM project that uses a scheduled trigger (e.g. it runs every day at a specific time), looks up the issues that have been in status "Successfully Solved" for at…

Hi @Mathew Kuruvilla and welcome to the Community! I am assuming that you have created Project bug as a sub-task issue type in Jira Settings > Issues > Issue Types? If so, note that you can indeed make this available in a project, as long as your project is company managed. You cannot add a centrally managed issue type to…

Hi @Jessica Brasington and welcome to the Community! That depends what a project is in your Jira instance. If it is an issue type (like an epic), you should be able to convert the project (issue) into an epic. Open the issue, click on the ... button near the top right corner of your screen and select Move: Select the Jira…

Hi @Smitha Joseph, Let's assume that user stories are an issue type Story in your Jira, just navigate to Filters > View all issues, switch to advanced search mode and enter the following JQL: issuetype = Story and assignee = <user> Obviously, replace <user> with the person you're looking for. Hope this helps!

Hi @Florian and welcome to the Community! No, there is no way to prevent the behaviour you're observing, except for starting a sprint - literally - when it starts. If you start a sprint and then add an issue to that started sprint, you add an issue after the sprint started. That is just the order of events. The dates of…

Hi @Spasimira Genova, No reason to go nuts 😛 - the problem is that (nearly) all statuses in your workflow have global transitions associated with them. These are the ALL boxes associated with every status. Just starting from your requirement: They want the status 'Waiting for support' to only be able to transition to 'In…

Hi @Jason McDermott, No. Jira Product Discovery is a separate Jira product (see Atlassian's product landing page), not a marketplace app. If Atlassian would retire a product, they would put a bit more effort in the message as well, I'm sure 😛 Hope this helps!

Hi @henal bangdiwala, This looks very much like your oAuth connection to your Outlook or Gmail is no longer in the air. Looks very much like the issue described in this support article, which also lists the steps to address this. Hope this helps!

I am not sure how your use case is different? If you configure the period settings in Tempo to weekly and set the scheduler to send a notification to late users, what it does is send a notification to those people who did not submit their timesheet on time. Unless I am missing a point, that seems exactly what you describe,…

Sure, @Anil Kumar. You can find instructions right here.

Hi @Sean H_ and welcome to the Community! I'm afraid you've answered your own question there - the list view is (currently) limited to a single project indeed. See this announcement article from when it was launched in Jira Software projects. Hope this helps!

Hi @Anil Kumar, If you talk about submitting timesheets for approval, you must be using a time tracking app. Could you confirm which one it is? If you're using Timesheets from Tempo, there is a built-in scheduler function that sends an email notification to the users themselves when to remind them to submit their…

Hi @Mohan Kona and welcome to the Community! If you want to find issues with no component on them, you need to search for them explicitly like this: Project = <projectName> AND Component IS EMPTY You can combine that with your previous search if you want to find issues with a different component listed than "Prod" Project…

Hi @aryder, I am not sure if I understand your question correctly, but you can (only) restrict the ability to create team managed projects by assigning groups of users to the Create team-managed Projects global permission in your instance. As an admin user, you can find this under Jira Settings > System > Global…

Hi @Sara, That is unfortunately not a search supported natively in Jira, but it can be done with marketplace apps like Scriptrunner or JQL Search Extensions. Hope this helps! 

In company managed projects, configurations are shared among projects through schemes. A status is linked to one/more projects as follows: * a status belongs to a workflow * a workflow can be included in one or more workflow schemes * a workflow scheme is linked to one or more projects The workflow scheme I mentioned under…

Hi @Adam Robert Corrie and welcome to the Community! Just a couple of pointers - you might benefit from working with a Solution Partner to get you up and running with all the details in place (working for one myself): * Your agreed agencies will need access to Jira to work with you. If you're using Jira, that means they…

Hi @Bryan Dsylva and welcome to the Community! Is this a team managed or a company managed project? Statuses for company managed projects are managed centrally in Jira. You can find them (if you have admin permissions) from Jira settings > Issues > Statuses. Statuses that are not being used in any workflows will have a…