Walter Buggenhout Community Champion

Hi @brian.g, While an administrator can set a default language for an Atlassian product to encourage the use of a common language across the UI, admins cannot enforce the language of a user's personal profile, as you can verify in this support article. You can of course strongly recommend your users to adhere to the…

Hi @Ramyasree.bale and welcome to the Community! The issue types you see in this list are made available in your projects via issue type schemes. That is, if your project is company managed. To make sure what type of project it is where you don't see the change issue type in the list, navigate to the board view and near…

Thanks for putting some effort in this summary, @Raul Pelaez _TecnoFor - Marketplace Partner_ - nice staring point now the GA was announced!

Hi @AT, before diving into your query, if you use Jira Software and use a Scrum Board, there is a velocity report out-of-the-box that displays your team's velocity across sprints. If you work in sprints that start on Sunday and end 2 weeks later on a Saturday, then your velocity report will display exactly what you seem to…

Hi @František Vůjtek, I ldon't think I fully grasp what you are trying to do here. From what you explain, it seems that the custom field DRP Approved - Delivery window is a dropdown. In other words: a select list with predefined values. If that is true, I don't think JQL will be able to interpret those values as dates, but…

Hi @Santhosh Raj, Your observation is correct: there is currently no way to filter the board view on date ranges and there are no board settings available to add your own filters. This may - to a certain extent - be because the goal of your board view is to mainly manipulate all open work (regardless of when it was…

Hi @HP, Considering your budget argument, I would assume your current instance is a Jira Server instance. If so, the license for the product is perpetual and that means the product remains in a working state even if you don't purchase a maintenance renewal (which is no longer possible anyway). So, technically, as long as…

Hi @Juan Gregorio Toro Ramirez , You can connect your Active Directory to Jira cloud using Atlassian Access. Once connected, you can use your AD users as if they were created directly in your site - as of then, you can use them in any user field in Jira (system fields like assignee and reporter, but also in any custom…

Hi @rubenag83, I am guessing you have created a team managed project from a scrum template. If not, check in the left bottom corner of your board to confirm what type of project you are in. A team managed project doesn't offer a swimlanes feature like the company managed project does. In board view, however, there is a…

Hi @Eric Roetenberg, No, unfortunately not (out of the box). Jira Software has a fixed issue hierarchy consisting of Epic >> Story >> Sub-Task. In the premium version of the tool, using Advanced Roadmaps, you can expand that hierarchy, but only above the Epic level. You can introduce additional levels there, but only above…

Hi @Suporte JRetail, It depends what field you have in mind. In the SLA configuration, you can see the list of events that may trigger your timer to start or stop running. When it comes to fields, assignee, resolution and due date are supported. If you want to use a different field, there is no out of the box support…

Hi @Abdul Wahith and welcome to the Community! From your screenshot, it seems that you are using a company managed Jira Software project. In order to create issues in a project, you must have create issues permission in that project AND have a Jira Software license. The most likely cause here (looking at your screenshot)…

Hi @Mujahid khan and welcome to the Community! What you can do first is create a saved filter with the following JQL: "completion date" <= startOfDay() AND resolution = Unresolved Save it, e.g. under the name Overdue stories and add a Filter Results gadget to your dashboard. Select that saved filter as your gadget source…

Hi @Lisa, That's a pretty tricky change (the update of the sprint badges based on status category). While it seems to make perfect sense at first sight ... * Many customers don't configure status categories properly. * Statuses are managed centrally in Jira and can only have 1 status category (and corresponding color…

Thx for sharing, @Matt Johnson!

I do follow to a certain extent, @Osman Beyaztas. As new capabilities emerge, I too sometimes wonder why certain new views are not shared across other products. The list view of JWM and its concurrent editing feature would be great for JSW projects as well, to name an example. On a side note: if there is one thing that is…

Hi @Emilia Mehr and welcome to the Community! If you use company managed projects, you can build separate workflow screens for each transition that hold just the relevant fields. With each transition, you can add workflow validators to check the required fields in that step. That seems like the exact match to your use…

Hi @Chris Mitchell and welcome to the Community! Short answer: don't. You seem to have just discovered how you can use releases manage versions. In practice, this is just the set of features you release together. A release (or version) itself has a start and release date. And basically all the issues you add to that…

Hi @Osman Beyaztas, Do you have an actual question we can help you with? The tools you mention all serve a certain purpose. Atlas e.g. does not require a project setup as you mention. It is a directory for your teams and a catalog where you can communicate status of your projects and goals. Jira Product Discovery is meant…

In terms of tools, it's pretty limited. The service desk is JSM premium, the categorisation is in Assets (part of the product), as it lets you set up multiple cascading custom fields to define the 3-level hierarchy. For the reporting, we used EazyBI.

What types of incidents / requests is going to be specific to the products and/or services you provide to your customers, I would assume. To give you a high level indication, the customer I'm referring to delivers both services, products and software. Under incidents, we categorised everything that could go wrong and…

Hi @[deleted] and welcome to the Community! If the project you are creating these issues in is team managed, check Project Settings > Issue types. Select the issue type you are creating and locate the Labels field. Expand its settings and update the default label(s) to the desired value. In the project is company managed,…

Hi @Sascha Schäfers, Setting the visibility of a filter or a board does not impact the visibility of the issues. It just impacts the given that a user can / cannot access the specific saved filter or board and those - as @Trudy P Claspill tried to explain correctly - are totally separate things from the actual issues. If…

Yet it does. In company managed projects, the link between epics and stories used/uses the epic link field, something that doesn't exist in team-managed projects. In team managed projects, these parent-child relationships are not recognised.

Is your project team managed or company managed @Matt Johnson? In my setup it does indeed work, in a company managed project.

Hi @Matt Johnson, At first sight I cannot see anything particularly wrong with your automation. I built a similar rule to check what might be missing and did more or less the same. The only thing I am sure I did differently, was add a check on the created issue type, so I am sure that I am validating a story: Also, check…

The build is complete, @Ditte Simard 🎉💥🎉 - I did not really keep a clock at hand, but it took us around a week (7 days or so), building between 1 and 2 hours on average each day ... On some days also spending half an our or so trying to find out why a few pieces were missing because we had accidentally used them in a wrong…

Hi @Resignola, Kelly, Not in the Team settings. One team can only have one issue source there. You can always build a filter or a specific board that brings the issues for a team together and then use that filter or board as the issue source for the team. In practice, it is a good idea to have a single board for a single…

Yes indeed, @Daniel Lim. That is correct! 

Hi @nathalia_fukuda, Technically, that may be fairly simple. But there is a difference if you are using company or team managed projects. Very complex flows are not very often found in team managed projects, so assuming that you are using a company managed setup, all you need to do (theoretically) is add a new board.…