Walter Buggenhout Community Champion

Hi @Ashok Shembde, The best way to get help for this would be to reach out to the app vendor directly. You should be able to find contact details on the app's listing page in the Atlassian Marketplace. Hope this helps!

Hi @Thomas A, I have a very strong suspicion that someone created an automation rule (with a scheduled trigger?) that moves tickets that are waiting to be closed to the done status after a certain amount of time. And maybe there is a flaw in that rule that accidentally also moves issues with status deleted along. If you…

Hi @Tzachi Gujski and welcome to the Community! There can be several different explanations, to be honest. I'm happy to list a few, but a bit more information might be helpful for better judgment: * Is your board in a team-managed or company-managed project? * Is your board a scrum or a kanban board? If it is a kanban…

Yes, I see what you mean. This is a gadget created with custom charts (a marketplace app) and it does indeed seem as if the results returned by the source filter (Jira data) and the visualisation in the chart (processed by the app) are out of sync. I can't think of any better cause than the 2 data points being refreshed…

No. The reporter of the ticket is not even known before an issue is created and automation rules act upon events; they do not manipulate screens while you are editing stuff. I am quite sure that the end result will be what you want (or even better). If it were possible to add the reporter to the summary field while the…

is part of "Trigger Issue" is doing exactly the same as if there would be something like is part of {{triggerIssue}}. You only need smart values if there is no other way of getting to the result you want. The problem here is that you need to be specific about the issue you want to link your current issue to. This…

It depends what issue you are trying to link to. In your screenshot, you are referring to the issue that triggered the rule (so essentially to itself). That does not make any sense. You need to be clear what issue you want to link to ...

Hi @lucia_plaza and welcome to the Community! I am not sure what you are referring to when you mention graphics, but it is true that dashboard gadgets are not updating in real time. Gadgets can be configured to refresh themselves, but there may always be a delay of up to 15 minutes: You can always manually refresh your…

Hi @Yousuf Al Rawahi, If your question is indeed about cloud premium, I would recommend using automation for this. You would need an automation rule along these lines: * trigger: issue created * action: edit issue, updating the summary field to the following: {{issue.summary}} - {{issue.reporter.displayName}} Hope this…

Hi @Aditya Singh and welcome to the Community! You should be able to trigger that with Field Value Changed, selecting the Fix Versions field with the option value added: Hope this helps!

Hi @Jayanth, I don't really see how you would collect all updates in a project, since that could indeed mean a lot of different things: * comments added * issues created * statuses changed * fields edited However, it is quite easy to pull a list of issues that were updated/created in the last 24 hours. You don't even need…

Hi @Sherwin Soriano, No, you cannot dynamically use the sprint dates. There may be other ways to get the results you are after, but I am not quite sure I understand your requirement in full. The following JQL returns the issues in your current sprint: sprint in openSprints() If you add a reference to a date, e.g. created…

Hi @Zulfiqar Ali Shah Kazmi and welcome to the Community! If you want to reference multiple statuses in a list, try the following instead: project = "Project Name" AND issuetype != Epic AND status IN ("Status 1", "Status 2") Use IN (...) and - if your status names contain spaces - use quotes. Hope this helps!

Hi @Susan Allaire and welcome to the Community! It looks as if someone on your Jira instance has configured this field to be required. I have not seen this field required in Jira as a predefined setting somewhere. This behaviour can either be the result of: * an admin setting the field as required in a field configuration…

Hi @gisele.galera and welcome to the Community! The label locked (or bloqueado) just means that these are Jira system fields and that you cannot change their configuration as an administrator. It does not tell anything about your ability to use (or not use) them on screens etc. It is true that these fields are no longer…

Hi @Margaret Boisvert, Since this is a request about a specific marketplace app, it is best to reach out to the vendor of the app directly. You should be able to find contact details on the app's marketplace listing page. Hope this helps!

Hi @sagelesko and welcome to the Community! Sharing filters with a team is today not possible. But there's a couple of workarounds you can use that are right there in your screenshot: * If you can create a group (in your site's user management), you can share your filters and dashboards with that group, representing your…

😀 Awesome, @[deleted]! Just answered that one in this other thread. But you're absolutely right to raise a separate question for it. Yes you can, but only as a Jira administrator using the built-in automation engine in Jira. Plans (Advanced Roadmaps) has nothing to do with automation. See this support article for more…

Yes you can, @[deleted]. But automations have nothing to do with advanced roadmaps (or plans). Jira has a built-in automation engine that is perfectly capable of automating actions within a single Jira project or across multiple projects. Cross-project automations can only be configured by a Jira administrator, though.…

Hi @SianS, Out of the box, Jira lets you use the original estimate / time spent / remaining estimate fields to track time or effort. It does not offer features to track this automatically, but there are many time tracking apps in the Atlassian Marketplace - some of them have trackers that can be started and stopped to…

Hi @Santiago Fernández, Jira Service Management is built to support all kinds of IT and Enterprise Service Management use cases. Incident management is just one of these use cases. There's an online guide on how JSM supports incident management and links to other supported service management processes from the navigation…

Hi @martin_lau, With that query you may still have corner cases, but it will probably be correct 95% of the time. Your JQL statement says that: * the current status is "READY FOR DEV" * issues did go through a transition before Sept 30th but it does not specify what transition this was and it does not say anything about…

Hi @[deleted] and welcome to the Community! That is indeed and absolutely true. You can find tons of information about the topic from this summary page in Atlassian's documentation. Hope this helps! Don't worry to add additional questions if they arise!

Hi @martin_lau and welcome to the Community! Have you looked at the Cumulative Flow Diagram associated with your project board? Hope this helps!

Hi @Ayush Lawania, You tagged your question as related to Jira Service Management. If that is the case and you have a time to resolution SLA in place, you should be able to leverage that to answer your question. The SLA timer should start when an issue is created and stopped when the issue is resolved. Once you have that,…

Hi @Lynique Heynes and welcome to the Community! Onboarding / offboarding processes quite commonly involve a lot of steps, interaction with multiple teams and plenty of needed coordination and collaboration. Jira & Jira Service Management can help you create control and visibility over these processes very nicely, but this…

Hi @Heather Barnes and welcome to the Community! As a first step, set up a first project and make sure you make it company managed. Configure all the settings the way you want your "standard project" to be. That means: * Configuring the desired issue types * Setting up screens with the necessary fields * Designing your…

That is quite easy, @Sandy Hsieh. Just drag the won't do status into the Done column on the board, right below the Done status that's already there. Then remove the Won't Do column from the board. 

Hi @suneel babu, That depends on many factors, such as how many users are involved, how many issues, attachments, ... are in the project, how busy it is on the interwebs highway, ... This may very between seconds and a couple of minutes, depending on some of the factors mentioned. Since I imagine you are planning to copy a…

Hi @Fouad El-Gendy, If this really is only happening with a single person, I would suggest he/she makes sure he/she is actually logged into Jira, maybe clears browser cookies and/or does log off and on again to make sure he/she is properly connected to the tool. If the issue still occurs after that and you are on a paid…