Walter Buggenhout Community Champion

Hi @Renato Rodrigues, The short answer is "yes". You don't need to do anything extra in the roadmap. It just reads the issue status from the issues in Jira. 

Hi @María Martha Roggerone, If I understand correctly, you created a next gen project and don't see the report option from the navigation bar on the left hand side? Navigate to Project Settings on the bottom left, select Features and then toggle on the Reports option:

Hi @Renato Rodrigues, When you change data in advanced roadmaps and then confirm to save those changes, everything you updated in the roadmap will also change in Jira. Usually these will be dates, or maybe the team or release you assigned. The only situation where you will see immediate impact on the sprint itself, is when…

Hi @Steven Kent, The hierarchy from Initiative down to Subtask is what you may indeed call a hierarchy. The default hierarchy in Jira (Software), however is just: Epic Standard issue types (story, task, bug, ...) Sub-Task You define additional issue types in Jira yourself with the names and meaning you like or prefer. So…

The question remains how you indicate or may retrieve that your team is working on that initiative. Since you seem to be using Advanced Roadmaps, you have the team field to indicate what issues belong with a team. How we usually set this up is as follows: * for initiatives that are worked on by a single team, we assign…

Hi @BrosseauDamien _Consultant_, This depends totally on how you associate issues to your team. If your team has its work in a Jira project called "XYZ" or in three different projects X, Y and Z, it could be as simple as this: Issuetype = Initiative AND Project = XYZ or Issuetype = Initiative AND Projects in (X, Y, Z) That…

Hi @Shekar S, The procedure to remove a product from your site is described in the documentation over here. Be aware that all data from Confluence will be deleted completed, so make sure this is absolutely what you want! Hope this helps! kr, Walter

Could you share some screenshots of your setup to help us diagnose further? Think: * issue sources of your plan * filter settings in your plan * hierarchy configuration

Hi @Urmo Luts, If you select the full hierarchy options in the filter settings, it should show you all issues connected to the filtered initiatives: A precondition is that the Epics and other issues are indeed linked to their respective parent issues, obviously.

Hi @Bruno Gasnier, I understand that all boards are associated with the same Jira project. It is important to understand that issues are created inside a project, while a board is essentially a view on those issues. Or in other words, you always create your issues in a project, never in a board. When creating an issue,…

Hi @Rajesh Jaggumantri, There is a technical side to this and a process side. Technically, it is perfectly possible to allow for tasks to be estimated in story points. It is just a matter of making sure the story point field is available on the screens you use for tasks in Jira. The process part is something else. In…

Hi @Георгий Пономаренко, Site admin and project admin settings are different things. Although it is quite common that site admins are also project administrators, project settings can be set up independently. If you say a change of security politics has been applied and group memberships have changed, then maybe the…

Hi @Flora , Definitely a good suggestion from my perspective too, but the Roadmap link in the sidebar is a different type of roadmap: the basic roadmap that is restricted to a single project. As a workaround, what you could do is add a custom link to the sidebar of your project with the Add Item option. Just name the…

Maybe I overlooked it, but I think I missed an actual link in the second quiz description. If I remember well, the intro text mentioned the Community Guidelines, but I can't remember it was possible to click through to the page, contrary to the way it's done in this topic. Could be helpful to show the link at the end,…

I've run through the quizzes and from a usability perspective just thought that there's a lot of clicking required to go through the steps. Answering and moving to the next question both uses the same Next button caption. I feel lucky vs next question already makes a difference there, if that were possible. I did like the…

Well done, all of you! Congratulations!

As a matter of fact, I was involved in a thread where I was on the end of being wrong myself. And I am not ashamed to share that and how I was wrong with my initial answer there: https://community.atlassian.com/t5/Jira-Service-Management/How-to-control-the-visibility-of-SLAs/qaq-p/1581354 The user who originally asked the…

Hi @Joe Sapinoso, There is no means to find out who deleted a page indeed. There's a documented workaround for the server platform, but that requires access to the database. However, in the assumption that you would like to recover the page: a deleted page is moved to the Confluence trash (space settings > content tools >…

Hi @Michal Blazejczyk, They clearly are :-). Could it be you have extension for Jira Service Management on your instance? The app adds additional features, SLA data on the portal being one of them. If that's the case, the documentation has more info on activating/deactivating this. 

Hi @Krzysztof Kiser, The behaviour you see seems perfectly logical to me. When you delete an issue, the associated worklogs are deleted as well. That last event then triggers this rule that tries to edit fields on an issue that no longer exists, which is obviously not possible. Unless deleting issues is a very common…

Any bold statements I'd make would honestly be wild guesses without any insight into your configuration. Adding a comment on your issues does trigger an update of the issue. So I wouldn't be surprised if somewhere in the back of your data set there is either some filtering on updated date or maybe an indexing problem in…

Hi @Ryan Liu, You are absolutely right that a wrong answer is - well - just a wrong answer. But we are in a positive place here, with a lot of people voluntarily spending some of their free time in the spirit of helping others to the best of their ability. In that sense, it's much more pleasant to highlight a helpful…

Hi @Michal Blazejczyk, If your external clients are accessing your servicedesk through the customer portal - which they should - they won't be seeing any SLA data as it is not disclosed on the portal. SLA timers are only shown on the internal Jira tickets to your internal staff. 

Hi @wrenitinfrastructure, This type of issues is always hard to diagnose without any insight into the actual data. Several things may cause your data to be hidden from sight (or from your plan altogether) * you say you added a filter to exclude completed projects/epics from the plan > that would be something I'd definitely…

Hi @Todd Randels, I am a bit confused about the Confluence and Jira part of your question. An option to deal with forms in Jira may be ProForma, as it has a Confluence style editor to design your forms, you don't have to link all fields in your forms to Jira fields and you can do all kinds of stuff with the captured data…

Hi @wrenitinfrastructure, If you are on server, go to your plan configuration and select issue sources from the menu on the left side of your screen. Click the big button to Edit issue sources and run through the import wizard again step by step. In step 3/3 filter the issues by Epic and have a look if there are unchecked…

Hi @Hanieh Katebian, There is an automation template library available with plenty of example rules that may inspire you. If I understand your use case well, if you create a new epic (or sub project) in your Jira project, you want to automatically create a set of predefined tasks inside that epic and specify a number of…

Hi @Nick van der Net, Saved filters are available through Filters > advanced issue search. Or when coming from the next-gen issues overview, by clicking the go to advanced search button in the top right corner. After defining your search and saving the filter, under columns you will find 3 tabs: The filter tab will only be…

@Jack Brickey, The hierarchy is only visible in its full glory in advanced roadmaps (or e.g in a marketplace app like Structure or similar, where you can extend the classic Jira hierarchy you refer to). In Jira you will see the initiatives linked as the Parent issue of an Epic. Stories can't be linked to initiatives…

Hi @Vishal Biyani, The proper way to solve this issue is to create a separate Jira project for your initiative issues (only the initiatives) and make sure the issue type scheme for that project only has the initiative issue type associated with it. That way you won't be able to associate sub-tasks with your initiatives.