Walter Buggenhout Community Champion

Hi @Gui Ávila, On a general note - it depends what you mean by public and who your users are. Your users may be people you know as they are your customers and they signed up for an account with you. Or they may be everyone in the world with access to / from the internet. JSM is not built for disclosing a public roadmap. It…

Glad that I could help! If it worked, would you mind accepting the answer here as well ;-)? That makes it easier to find for other users with similar challenges. All the best in making your tools work in the best possible way for your team!

Hi @sandhya mohanty, The page from cloud documentation you refer to is just the core functionality used to create, edit and update pages in Confluence. Out of the box, nothing fancy there. You could just as well replace Publish with Save and have a good idea of what the button does. There are no plugins involved, neither…

Hi @TSNakamura, No, they won't be updated automatically. This requires a scripted update behind the scenes once the migration is complete and you'll need to involve Atlassian support for that (at least if it's many updates). Create a ticket for this with Atlassian Migration support. They will be happy to perform the update…

Hi @Yatish Madhav, I would recommend you create a ticket directly with Atlassian support for this. They will be able to investigate the best path forward with access to your data and give proper advise on the migration path. Choose migration support as ticket type or technical issues related to Atlassian Access.

Hi @kerensho, If the main thing you want to do is calculations, then make this a numeric field and put the legend in the custom field description. That way it will be shown on screens just below the issues. 

Hi @Michael Priest II, That is an interesting case you have here. As I was triggered (pun intended) by it, I tried to set up something similar in a test instance, to find out afterwards that I was in a Next-gen project - but that shouldn't matter for the rule. I came up with this, which led to a working result: A couple of…

Hi @Rachel Grundy, Unfortunately this is not possible in Jira Cloud out of the box. See JRACLOUD-7266 and the referenced issue JRACLOUD-1369 that was considered higher up on the priority list, but still open. Workarounds may be possible with built-in Automation (you can customise email notifications using smart values) or…

Hi @Rob Green, Never mind and welcome to the community. There is indeed quite a bit under the hood to get everything in place just the way you want it. There's a couple of things you need to get this reopening functionality to work: * your workflow must allow a transition (a path) from resolved status to an open status in…

Hi @Irina Stepanova, It depends a bit as to what you understand by template. It can be a a single issue with some pre-filled bits of text or certain default values. It can also be a structure of several issues. Depending on your scenario, several options exist in the marketplace. Have a look into some options here.

Hi @lisa, As it seems you are on the premium plan, this is default functionality of the included Advanced Roadmaps. This page from documentation is a specific answer to your question. However, take some time to checkout the full documentation or take a look at this video to familiarise yourself with the tool if you haven't…

They should recalculate, as long as they match the triggers and conditions specified in your SLA. I have read that the process may in certain cases take a long time. Just in case, some additional references: * JSDSERVER-6238 / ticket referring to the slow calculation times * troubleshooting missing or corrupted SLA data 

Hi @Kaur Joakit, The SLA will not recalculate on issues that have been resolved previously. That is just by design. They were resolved against SLA metrics that applied at the time, so the resulted is already locked into the history of the system. 

Yes, but it seems it is the correct board though. If you switch to backlog view on the board, you are in the correct project I assume. Feels like you hit a bug somehow, if you ask me. I guess what I would do is to create a new sprint, update the sprint value of the issues (from your issues themselves, not from the board…

Hi @Lea Stjepovic, Thx for sharing the screenshots. As you - rightfully - blurred out a lot of information, I'm still not sure what I am looking at. I guess what I see on the right hand side is a task that belongs to an Epic. And if I understand you correctly, that task is nowhere to be seen, not even on the backlog? I…

Hey @Daniel Tranca, I am 100% sure they do - computers are always right, you know ;-). But it is true that we haven't found which one it is yet. As these are Epics which I can see are collapsed in the roadmap currently, what scheduling information do you see from the underlying issues? Either fixed or auto-calculated. 

In case re-ranking does not fix the issue yet, have a look at this page in the documentation - it explains a lot about the scheduling features. A small extract, which may be key to analyse what is going on in your case: When auto-scheduling the issues in a plan, several factors are considered: * how your teams work, i.e.…

That's not it then. The calculations used are a complex matter, taking a lot of factors into account. Dependencies are just one of them, so there will be something else determining the behaviour. Could you check if changing the order of issues has an impact? Just drag KW-1 below KW-6.

Hi @Daniel Tranca, Could you have a look into your plan settings by clicking the cog wheel next to the plan's title. On the Scheduling page, have a look at the setting for dependencies and verify if it is set to sequential:

Hi @tejashree avinash aringle, I certainly can. Could you raise a new community question for this? This is an old question that has been answered long ago, so not really the place to keep adding new stuff to. Feel free to mention me in your question. I'll be notified when it comes in (normally) :-). 

Hi @[deleted], There are definitely ways, but they won't necessarily be easy. * If your client's Jira is a virgin instance with nothing in it, you could backup / restore your entire Jira (but I guess that scenario is unlikely) * You could export your project data to csv and import the csv data into you customer Jira, but…

Hi @Uma Sanjeevi, No, not as far as I can see. What is in progress is in the progress column. Filtering and sorting can be done on issue type, assignee or keyword, Epic or Version if you use those. In backlog view you can enable the epics or versions panels, but that's it I'm afraid. 

Hi @SHRIKANT SHET, Welcome to Jira and welcome to the community This is almost a consultancy question, to be honest. But nevertheless, let me give you a couple of pointers here: * Don't use 10 different boards to manage the work of a single team, but try to consolidate this into 1 or 2 (a board can get its data from a…

Hi @Elizabeth Howden, I would be really happy to join the club of migration MVP's > Here is my article comment: https://community.atlassian.com/t5/Atlassian-Cloud-Migration/Evaluating-Jira-Cloud-with-BI-tools-Here-are-some-options-to/ba-p/1253333#U1543227 > And two answered questions as well:…

Although this is a somewhat older article already, I like the overview of BI reporting options in a single place here, cross platform even. Good starting point and relevant links to start digging into the options!

Glad I could be of assistance, @Simon Müller Would you mind accepting my answer as well? That does help other users with similar questions finding answers easier; Thx! 

That is a good and valid point @Sarath. At the same time be aware that once fields are on a screen, to a user there is absolutely no difference whether a field is a default field or a custom field. It is just something they need to fill out when they create or update an issue. So to them, it doesn't affect anything really…

Hi @Gan Zhi Long, I understand you refer to the following dialog you ran into while trying to configure the filter source for the report: First, let's make sure you understand what the report actually does. It will essentially pull you a list of issues, group this by a custom field of your choice and display percent…

Hi @John Mustac, No. Automation for Jira DC will still be a separate Marketplace app. The rebrand of Jira Service Desk to Jira Service Management IS part of the 4.14 release. See the release notes and upgrade notes for things to consider. 

Definitely @Kristen Roth , I like the focus on different aspects of team health while you keep it pretty limited as well. I think I am going to suggest something we try something along these lines. I am a strong believer that remote teams should commit more to asynchronous communication. Not to replace the physical touch…