Walter Buggenhout Community Champion

Hi @[deleted] and welcome to the Community! No, unfortunately not. The filter that you use to retrieve the data for your report returns issues, which are then plotted to the X- and Y-axes of the gadget by sprint and issue type (on these issues). If there are no missed issues in a sprint, your filter won't return any and -…

Hi @Matt Noe, A lot depends on how you work, how these vendors access your Jira instance etc. But based on what you describe, it feels quite natural if you had separate tasks for each vendor. They could be sub-tasks to a general standard task, or they could be standard tasks below an epic. Anyway, giving each vendor a…

Hi @Azandè Caldicott and welcome to the Community! There's quite a few different product (Jira Software, Jira Work Management, Jira Service Management, Jira Product Discovery) and project (Company Managed, Team Managed) types in Jira, all having their own peculiarities when it comes to settings. Since Epics are essentially…

Ok. If all goes well, @Rakesh Pradhan, converting a task into a milestone in BigPicture should add a #milestone label to that task in Jira. That should allow you to create a quick filter that looks for that specific label in Jira to highlight just your milestone tasks like this: labels = "#milestone" Hope this helps!

Hi @ADEEL AHMED, That is a very open ended question. When it comes to automation, understand how you want to work first, make sure you determine how you want to work first, build some stability into your processes first and automate repetitive tasks later. Automation is a low to no code platform component that lets you…

That's exactly what the technique is for: you let people (blindly and personally) show a card with their estimate on it. If your estimates are alike, then you know you have consent among the team members about that estimate. If you see significant differences, you discuss these differences as a team. The goal is to promote…

Hi @Rakesh Pradhan and welcome to the Community! All comes down to how you define milestones and what you mean by gantt view. Are you using advanced roadmaps or a marketplace app? Are your milestones a certain issue type or are they something else?

Hi @ADEEL AHMED, Agile poker or planning poker is a technique to collaboratively estimate work for your team. It is not something that is natively available in Jira. In the software teams I used to work with, we often used a physical card deck to do the estimates, but there are several marketplace apps available that let…

Hi @Florian Winkler and welcome to the Community! This is certainly not a paid feature. The labels filter automagically appears in your backlog view as soon as you have at least one issue in your project with the labels field filled out. Use the built-in labels field to add labels to your issues. Hope this helps!

Hi @jaafar Hosni and welcome to the Community! I am not sure how automation for Jira fits into your use case, here. You create the hierarchy (i.e the configuration) once in your Jira settings. When you then create issues at the appropriate levels and link them via the parent link field, they end up in the right place in…

That is not something you'd be able to do with standard, out of the box reporting gadgets in Jira. It looks very much as if you're trying to do some delivered on time type of reporting, which you probable want to run across multiple issues at once? That type of reporting is possible with more powerful reporting tools that…

Hi @Claudio Guzman and welcome to the Community, From your description, it seems that you are trying to do something that is not possible in JQL. Calculating with dates and conditionally doing something else is not supported. Maybe using a reporting tool that lets you use formulas or exporting your data to excel may turn…

Hi @crvuong and welcome to the Community! A couple of things I would like to point out. Could you confirm that you are using a company managed project (not team managed)? If that is the case, updating an issue type scheme requires Jira Admin permissions. From your question, it looks as if you don't have them. And if so,…

Hi @Gopi L , While I don't see a gadget that does exactly look like you want, you can come very close with a two dimensional issue statistics gadget where you define: * Status as the X-axis * Epic link as the Y-axis The gadget may look somewhat like this: For each epic you can see how many issues are in each status. Hope…

Hi @Tamar Peer and welcome to the Community! I assume your are asking about an option to reply to an existing comment and as such create a discussion thread? If so, that is currently not possible. There is a feature request open for it though, that - while not on the short term roadmap - has been recognised as a valuable…

Yes, indeed. The description field (the body of the email) does not have a timestamp. But the created field on the ticket shows you when the issue was made in Jira. Any changes that occur to the description afterwards will be traceable on the history tab of your issue, with time indication.

Hi @jmercado, There should normally be at least some kind of indication of when the comment was added. It may however be that the time of creation is displayed relatively (as you can see in this example): By hovering over the relative indication (in my case: 1 second ago), you can see the actual timestamp appear. Hope this…

Hi @SQAMonkey, The simple answer is no, you cannot use a single field multiple times on the same screen. As a workaround, you may want to set up a multi-select list custom fields that holds the list of available parts and lets your users select multiple options from that list. Hope this helps! 

Hi @Josh Kinney and welcome to the Community! As you put it, developer 2 is responsible for code review. He/she supposedly ends that review with a conclusion to that review: ok or not ok. Seems to me that the person doing the review is the one who moves the ticket back to developer 1 (in case of problems), or indicates…

Hi @Glenn Samuelsen and welcome to the Community! The backlog you are referring to is a feature of your project (or team) board. It uses a mapping of the US workflow to a column of your board. For issues to appear on the board's backlog, they must be: * retrieved by the board's filter (which can be set via Board Settings >…

Hi @CHINNAMUTHEVISAI.SATYANARAYANASHARMA, As from JCMA version 1.6.2, there is a dark feature available that supports dashboard migration. That it is a dark feature usually means it is still experimental functionality and it is important to consider it as such. Have a look at this support article to learn more about what…

Hi @Lars Swart, Jira cloud has a message custom field available that you should be able to use for this use case. The default value you set in the field configuration will appear as the message. There's to flavours of the field available: You can find this field type when creating a new custom field under advanced field…

Hi @Tobias Dobberphul and welcome to the Community! Boards are fundamentally views that are layered on top of the issues that you have in a project. With a board comes a set of additional features, like the ability to plan sprints, see reports, etc. Filters (JQL) determine which issues appear on a board. And as soon as you…

Hi @Danno, Project settings are in a different place in JWM than in JSW. They are in the top navigation amongst the selection options for all different views. If your project is Company managed, then removing an issue type works in the same way as in JSW: remove the issue type from the issue type scheme your project is…

Hi @DigiBee Network and welcome to the Community! It seems as if you modified the workflow of your project. When you do so, you also need to map the statuses of your new workflow to the columns of your scrum board. Probably that is what is currently missing. To do so, navigate to your board, hit the ... button near the top…

I was one of those people who didn't make it out of the resort last year. But what a buzz it was and looking forward to this edition so much! Seems the death star has come quite a long way since last year. This was the view I had from my room 12 months ago:

Hi @Gustavo Lava, I hope it is okay for you to receive a reply in English? If you are on a free plan - as you mention - you can only use the basic roadmap for a single project. Depending on the type of project you use, you can enable it as follows: * In a team-managed project, navigate to Project settings > Features and…

Hi @Daniel Martinez, Check the options mentioned by @Mikael Sandberg if your ticket has always remained inside the same project. If that does not explain what happened, verify if the ticket wasn't moved from another project where it already had a resolution set. You should be able to validate all steps the ticket went…

Hi @Kelly Carlson and welcome to the Community! The answer to your questions relates entirely to how you define released issues. Jira has an advanced JQL function that lets you identify these issues like this: fixVersion in releasedVersions(ABC) ABC in that JQL represents the Jira project your issues are in. And it does…

Phew, now I am with you 😅 To set a user customfield, you'll need to use a syntax like this: "customfield_11453" : { "id":"2s1863211f0z284c45269423" } Where the first part represents the tester custom field and the second part is the account id for your test person. You may have found this documentation already, but…