Walter Buggenhout Community Champion

Hi @Ярослав Л, Welcome to the Community and great to see the recurring tasks challenge :-) There are many approaches to handling recurring tasks in Jira, which is probably why the marketplace offers several apps, each with there own unique approach to offer a standardised way of scheduling. I am happy to add a list with…

Hi @Karolis, Watchers is just a column you can display in search results of any filter and that you can sort by. I tend to agree with @Ismael Jimoh that votes may be a more significant metric to prioritise requests by, technically you can perfectly order the list of your requests by either watchers or votes. In the example…

Hi @Anumalla Nithinraj, This is a known limitation in the issue navigator for performance reasons. There is a ticket JRACLOUD-45639 regarding this issue. You can use the filter for use in dashboards, though - as you can see in this example:

Hi @ayesha, For this specific request, the answers suggesting to use apps are correct. Jira has no way out of the box to send email reports containing dashboard gadgets. Out of the box alternatives that are available: * you can share your dashboard with other people and educate them to view the dashboard itself directly in…

Hi @Paul Dymecki, These seem like clear metadata for your files/pages to me. I would recommend you to take a look into the page properties macro to add those structured data to your pages. In short, the macro lets you add a table with property names and values to the top of your page. See this example to illustrate: You…

Hi @uday, Your filter should look something like this: Project = AB AND issuetype = XYZ AND assignee = CurrentUser() AND due >= StartOfDay(3) AND due <= EndOfDay(3) Save the filter and make sure to share it with the people you want to notify. Then add a filter subscription. Either each user you want to be informed could…

Hi @Alexander De Leeuw, I assume you have already checked out the documentation on time tracking on this page. If not, definitely look into the sections on permissions and enable time tracking in projects. I would like to add there is a big difference between team managed (next-gen) and company managed (classic) projects.…

Hi @Justina.goldaracena, Have a look at the reports section of your board. If you don't see any reports yet, navigate to project settings and enable reports for your project. There is a burnup and burndown report available that has most of that information available. You can select the sprint you want to see from a…

Hi @dave, I think the reason is that resolved is actually a Date/Time field. I did a small test in a local instance to notice that the following statement did not return any results, as you describe too: Resolved = 2021-04-06 I did locate an issue that had 2021-04-06 09:50 as resolution date. But the database is even more…

Hi @Margaret Hodges, I am not sure about a JQL statement that would search back exactly 36 hours from now, but the following will get you quite close: Project = <your project> AND Sprint in OpenSprints() AND WorkLogDate >= StartOfDay(-1) Sprint in OpenSprints() will dynamically fetch the current sprint. WorkLogDate >=…

There is one more thing I can think of to check, @Robb Robins. Can you make sure that the scrum board that holds the sprint you are assigning issues to in Jira is set as (one of) the issue source(s) of your plan? If that were not the case, your plan would not be aware of the existence of those sprints, I reckon ...

I have been playing around a bit in a test instance to see what might be happening. It seems to work for me as described in the documentation. But I did ran into an interesting mismatch at a given point, when I found out that my board had issues from multiple projects. I had apparently wrong figures to, until I found out…

Hi @Robb Robins, I have an instance at my disposal and dates do get updated when I move issues to a different sprint. To be entirely correct: the due date gets updated (not the start date). Issues that get their dates from sprints are marked with an S lozenge alongside the dates:

Hi @Brendan Howard, The sprint health gadget status colours are based on the column configuration of the scrum board that holds the sprint. For an issue to be considered as done, it must be in the rightmost column of the board. this support article going back quite a long way into Jira history has a pretty good explanation.

Hi @Earl Griffin, It might be a better idea to create a backup of instance A and restore it into instance B. That should keep the name of instance B, but entirely overwrite it with the contents and settings from your backup. The procedure is described in this support article. Don't hesitate to reach out to Atlassian…

Hi @Robb Robins, About your first question, the new interface of advanced roadmaps uses formal target dates which are stored in custom fields (e.g. target start and end of start date and due date). Whereas in live plans the timelines were calculated all the time, the new plan builds its roadmap from those dates. And…

Hi @Shaun McGuire, Your advanced roadmaps plan acts as a sandbox environment. Everything you create or edit there can be undone - or pushed to Jira when you feel you are ready. In the top right corner you should see a big blue review changes button. It opens a dialog with all the changes you made in your plan. Hit the Save…

Hi @Ryan Marshall, Reopening a sprint in team managed projects is not available yet, unfortunately. On the positive side, there is a feature request open for it with reference JSWCLOUD-17208. On an even more positive note, it seems to be in the works right now. And to conclude with the best news of all, a comment dating…

I forgot to mention that the sprint from Project_A will only become visible in the board of a single project after at least one issue has been assigned to it. You can however add issues to that sprint from the side panel, as you can see in this screenshot:

Hi Fred, I am not sure if I understand your entire use case, but assuming that Project_A holds the board that groups all your projects, creating a sprint only on that board should make it available for your separate projects as well. Sprints are visible across Jira anyway, so it is no problem at all to assign issues from 1…

Hi @Michael Bagisha Bumba, JQL in general always returns issues. The search on WorkLogDate may in that sense be somewhat confusing, as it could make you (or many other people) think you will see worklogs being returned. The search you mentioned: WorkLogDate between 03/01/21 and 03/31/21 will return any Jira issues that…

Hi @Urmo Luts, Navigate to your plan settings (next to the plan name, click the cog icon and select configure). Then, from the left hand side menu, select removed issues. You should be able to find them there and re-include them in your plan. 

Hi @Jaqueline Frondola, That is a fair observation, which is due to the fact that your data are initially wrong: if your Epic's due date had been 5/05 from the start, the update of your other story's due date would not have an impact on the Epic at all. But since you did not have this rule in place before, your historic…

Do have a look at Analytics and EazyBI (demo account). Both include export options for your data and allow you to focus on end user activity.

I am not an API expert, but the Confluence Cloud API is documented and does have a set of audit records calls available. See the developer docs for more details.

Hi @Muffex, From the support article I shared, towards the very end: The audit log doesn't record information directly relating to pages such as page edits (you can see these in the page history) location, or changes to page restrictions. By default, events are removed from the log after 90 days. You can choose to keep…

Hi @Erik Meegdes, It seems there is an issue currently that caused Atlassian to - temporarily - disable the comment sorting feature: I am sure this should be a temporary issue. Keep an eye on JRACLOUD-73076 to stay informed of any changes. 

Hi @Muffex and welcome to the community, In cloud, you don't have access to the database. If you are an administrator and are not on a free plan, you can access the audit log. You can read more about that in this support article. If research on user behaviour is what you are after, another source of information could…

Jira out of the box has the affects version and fix version fields for this. Affects version would be the build a bug was identified in, fix version would be the one that contains the fix. The advantage of using those, is that you can also use the release hub and several built-in reports to track your release status,…

Hi @Alton Johnson, From this related question it seems users can view their active sessions, but not close them. From that same question it also looks as though you can reach out to Atlassian support to have them closed for you. As an alternative from this support article, changing your password is apparently a (maybe…