Walter Buggenhout Community Champion

Hi @Andrew Schaedler and welcome to the Community! Just correct the story point estimate to whatever it should be and don't worry about your burndown chart. Your job as an agile team is to deliver working software and give value to your customers, not aiming for the perfect burndown chart. If you need an explanation for…

Hi @Audrey Bay and welcome to the Community! No, quick filters are features specific to boards (unfortunately). So they have to be defined on each separate board, alas. Hope this clarifies!

Hi @Aykan Inal, Searching by Portal Group is not supported in JQL, unfortunately. In this related thread you may find a manageable workaround, either by listing the different request types in a group or by creating an additional custom field to recreate the grouping. Hope this helps!

Hi @Manuel Urbano Stordeur and welcome to the Community! The guide you are referring to is for Bitbucket and Jira Software Data Center / Server, while it seems you are using cloud. These are technologically different products with different feature sets. So make sure you are checking out the guides that match your…

Hi @Ivan Andrieiev, To be able to help out, can you be more precise about how you define "a closed task" ? For your scrum board, a task is considered closed when it is in the rightmost column of your board. If you have a closed status mapped to a different column on the board, that will not be considered closed by the…

No problem, @Mirela Todorova , it's still all in the filter settings. If you extend the filter I shared earlier, you can further restrict the set of issues to the one's your are watching: Project = "Your Project" AND labels = TeamA AND watcher = currentUser() This last bit is dynamic, so it will show the issues watched by…

Hi @Yarisma Mendoza and welcome to the Community! When you say "you can't use issuefunction", are you aware why you can't use it? It is a part of marketplace app scriptrunner. It is worth checking if you have the app available on your site or not. Comparing dates is not natively supported by JQL. While you could search…

Hi @BASTIEN DELOURMEL, As noticed in the issue referred to, there is no real workaround. The simplest way to fix this, is make your descriptions shorter, so they won't be truncated. As your question seems to be about the JSM portal, you could use the description field in the request form to provide additional details about…

All the best in getting this resolved asap, @Dhaval Vala! 

Hi @Cody Stokes and welcome to the Community! What you describe as the capacity management page is a view in an advanced roadmaps plan. When you are in that plan, next to the plan's name at the top of the screen, you should be able to access the Plan settings. In plan settings, select issue sources and find out if there…

Hi @Liane Walker and welcome to the Community! This is most likely linked to the way you have configured issue sources of your plan. Sprints are a feature of a scrum board, and they would normally be loaded into your plan automatically when you choose a board as an issue source. Check your plan settings / issue sources and…

Hi @Karina Steffano, You can use workflow properties to restrict certain actions when an issue is in a certain status. Assuming that this applies to completed issues, you could add the following property to the statuses of your workflow where you no longer want people to add hours: jira.permission.work.denied To do so:…

Hi @Steve Zielinski, Advanced roadmaps has a hierarchy that you do not see in the issue navigator in Jira. If you limit your view of issues to just the story level, ORDER BY rank in JQL should come pretty close to the same order you see in Advanced Roadmaps. However, since - as I mentioned - in advanced roadmaps the parent…

Hi @Dhaval Vala, Reach out to the app vendor of xray directly regarding this issue. You can do so via their support channels, which you should be able to find on their Marketplace listing. The Community forum is happy to help you out with all sorts of questions on best practices, how tos, to a certain extent even technical…

Hi @Mirela Todorova and welcome to the Community! Just assuming that you mean gadgets on a dashboard, in the scenario you describe you could basically use any widget and just create separate filters for each label. To be more precise: let's say you want to display a list of issues, you can use the filter results gadget.…

Hi @Tomasz Jurek and welcome to the Community! No, simply put there is no (simple) way to do this. Logged into Jira Software, you can either see an issue or you can't. There is no way to display part of an issue. Which makes sense, I would dare say. I would suspect that showing status - and nothing else - to your involved…

Hi @Clare, Your question leaves a bit of room for interpretation, but under view settings, you can select colour by | issue type to enable colours for different issue types. As you can see from the screenshot, there are plenty of other options that let you define the colouring preference of your choice to get more…

Hi @Ernest Kurmel, If you use an SLA calendar in your JSM project that looks like this: i.e. you specify your lunch break in the SLA calendar, then you can update your JQL condition to the one I shared previously. It will take your lunch break into account, as the SLA timer will be paused automatically outside office hours.

Hi @Ernest Kurmel, Assuming that you have set up your SLA with an SLA calendar with business hours defined, there is an advanced JQL function that you can use to determine whether an issue is created during those business hours and incorporate that in your automation rule like this: * Trigger: issue created * JQL…

Hi @Misty Meyers, you can make the automation rule a global rule. In the configuration of the rule, you can specify which projects it applies to, but indeed, given your scenario it must be enabled for all projects where you want to detect the (potential) creation of new versions.

Hi @Sean van der Leeden and welcome to the Community! The other domain is probably claimed by the other organisation. That means that you cannot manage the user's account, as it is owned by the other organisation. You should however be able to grant the account access to your site, but you should do so (as the message…

Hi @Misty Meyers, I actually found a slight hack to make this work. My automation rule looks like this: The hack relates to the for JQL branch that is needed with the Version created trigger of the rule. In order to use the version smart values to create a new version, you need to provide a list of issues in order to…

Hi @Amruta Abhyankar and welcome to the Community! You are a bit on a wrong track there, I'm afraid. JQL (or Jira Query Language) just helps you define search criteria to find (a list of) issues. It does not update anything for you. Another issue with your question is that you cannot create tasks under a story. Those would…

Awesome! Great that it works out!

Hi @Maroun Maroun, also to clarify: you don't create a sprint in a project. You create a sprint on a board (that is a different thing). And indeed, sprints from other boards do not appear automagically on other boards. But it is possible to assign an issue to a sprint by editing the sprint field on that issue directly (in…

Hi @Maroun Maroun, Sprints are a global concept in Jira. You create them from a scrum board, but they are visible across the entire Jira Software product. And they have to be, because (in company managed projects), teams can and should be able to fill their backlog with issues from multiple Jira projects. As sprint…

Hi @tvishakha, Jira has no native support for searching the last commented date. If your team does not have the habit of commenting on issues, it is not unlikely that they do not update tickets in other ways either, so checking for the last update may give you a first indication as well. The following JQL would return a…

Hi @Samuel Prathipaty, A common practice is to calculate the priority automatically from a combination of impact and urgency (or a combination of more objective criteria you prefer). Since the Priority field is a system field, you cannot make it dependent on another field (at least not of the box and marketplace apps still…

Good to see you are aware of best practices around performance, @Avinash Gulumbe . On the other hand, don't overdo it either! Adding one field (or even a couple) will not kill your instance. If you want to apply a different field name to a custom field, that usually means it is really a different field. You can mitigate…

Hi @Avinash Gulumbe and welcome to the Community! I am not sure if I understand your question correctly. But I seem to understand you have updated the field names on the request types in your JSM project. In my mind that means adding a customer friendly name to those fields in Project Settings > Request Types, where you…