Walter Buggenhout Community Champion

Hey @Eric Roetenberg, Zoals je correct opmerkt zijn Epic Name en Summary 2 verschillende velden in Jira. Bij creatie van een Epic zijn ze allebei verplicht in te geven (summary is de titel van je issue, de epic name - doorgaans - een verkorte versie die wordt weergegeven in de gekleurde lozenge op de onderliggende issues).…

Hi @Administrador de Jira GA, I have the bad / good habit to try and understand why people want to do certain things and what problem they are trying to solve. In this case, I am struggling a bit with that :-). If you have 16 SLA's, is that because you have a really large workflow that you split into several smaller…

I more or less felt that one coming, @Sam Elmeswari :-) Having 2 boards on one project is not the most common scenario, so it depends a bit on what you want to do. Let me give you 2 potential use cases: * Let's assume you have stories, tasks and incidents in the same project and you would like to apply scrum for stories…

Hi @Sam Elmeswari, As long as you are in a company managed project, yes you can.

Hi @Maria Consuelo, If you are using a company managed project, you can use the control chart report to get an overview of Lead (and cycle) times: This is a very powerful report, but you'll have to take your time to get familiar with how it works and how you can interpret all the information on it. So definitely take a…

Or from the Epics panel in the scrum/kanban board of a company managed project, you can still select a color from the little color marker next to each epic:

Hi @Laurie Anci, Just on the issue card itself, click the coloured square next to the issue title and choose from the available options: Hope this helps!

Hi @Mats Ljung, You are in a team-managed project. Workflows are much more limited than in company managed projects. The latter do have post functions. The one you have in your screenshot uses rules to do some very limited kind of post functions: edit an issue field or update the assignee. Hope this helps clarify!

Hi @Marian, This may sound disappointing, but there is no standard answer to that question. Except something like this: the best reporting tool for your executive team is the one that gives them the information the need to make decisions based on the data they need, as close to real time as possible and at the right cost…

Don't feel silly @Alejandra :-) - those who never ask a question will never get smarter (or it will take them much longer at least)!

Hi @Gajanan Sasane, There is no such thing as a move page permission in Confluence. The ability to move a page is related to the add and delete permissions a user has in both the source and target space. From the Confluence documentation: The best way you could achieve your goal, would be to restrict the delete page…

Hi @lenivins, If you really want to add a new site with a brand new url, just navigate to https://www.atlassian.com/software/confluence/free and walk through the steps to spin up a new site. You'll have to enter your email address and the site name and you should be up and running in just a couple of minutes. Just out of…

Hi @Ken Young, There is a feature comparison article in the support documentation that lists the differences and priorities. This section is about integrations: A Confluence cloud macro should be coming along (the 3rd column indicating that integrations are a priority area is about the cloud premium and enterprise plans).

Hey @Bill Sheboy and @Levente Takács, I can't reproduce the issue myself, but totally believe you are in the situation you describe. I've reached out to Atlassian to help clear out the issue. Stay tuned! 

Ji @Levente Takács, I found a setting that might help in Jira settings: under New issue view transition there is an option to move all users to the new view. Maybe that helps, but I am quite sure that even if you don't do anything you'll wake up with everyone on the new view automagically, if that is not the case yet. 

Hi @Jeanne ROBERT, No not yet. But there is good news: the very long outstanding feature request for this JRACLOUD-17783 has moved to in progress, as an update from March 21st on the ticket shows. So hold your horses and watch the ticket. It should be coming as a feature fairly soon. 

Hi @Sven Pardijs, Have you taken a look into your custom field context (only available if you are using company managed projects)? You can find those in the configuration of your custom field and they allow you to set visibility and even selectable options per project / issue type. Have a look at this support article for…

Thanks, @Ilan Brender. May I also ask you to mark my answer as accepted (given it seems to have helped you ;-)) - that makes it easier to find for users running into similar problems.

Hi @hristo.iliev, That is hard to tell, but I would not expect the update to take more than 15 minutes. Normally, the update will only update the SLA timers on open tickets - closed tickets have their SLA from the past and won't be updated. So that should limit the time for updating. Also, this update is running behind the…

Hi @Nazeeruddin Mohammed, You can do this using smart values: {{initiator.accountId}}

Hi @Glazner_ Dave _TR Commercial Excellence_ , Adding to what @Bill Sheboy mentioned before, I would even more encourage you to have a look at the Velocity chart. It is also a standard report in both team and company managed projects, as long as they are configured to use sprints. They are the exact representation of…

Hi @Kevin Cousins, Jira works best when it is setup to support your internal processes and teams, not the other way around. Apart from tons of product documentation, Atlassian also has some great guides on processes and ways of working. As a development organisation, you could definitely find a lot of value in this Agile…

Hi @Nazeeruddin Mohammed, In the history tab of your issues, you can see that the information is being recorded by Jira. However, you rightfully observed that there is no readily available field that you can use for out of the box reporting on it. There are some solid reporting tools out there that enable you to report on…

Hi @Ilan Brender, Oh, my apologies and thanks for clarifying ! I was assuming you were on the premium plan and using advanced roadmaps. I was referring to that functionality in my answer. Could you check if you have enabled the backlog of your board? Because if you do, your issues will appear in the backlog view, not on…

Hi @Britt Cromie, Your observation is correct. Sprints are accessible across boards and there are definitely use cases where this is a good thing (e.g. for teams working across multiple projects, like many - if not most - teams do). Having said that, there is a feature request to improve on this in the…

Hi @Ilan Brender, Issues created in the roadmap view are not saved instantly in Jira. As soon as you add / update any data in your roadmap, you should see a big blue button light up in the top right corner: Review Changes: When you click that button, you will see an overview of all the changes you made in your plan. When…

Hi @Peter Cheng, Welcome to the Community. If your test project is a company managed project, you should add the issue type bug to the issue type scheme of your project. The easiest way to do so, is to navigate to project settings > issue types and from the Actions button near the top right corner select the option edit…

Hi @Levente Takács, The switch to the new issue view has happened on March 31st. It is no longer possible to switch to the old view instead. 

Hi @Daniel Vaca, I see you shared a screenshot of the basic roadmap in Jira. And although it looks nice, it does not offer the advanced functionality you seem to be hoping for. The timelines are based on start / due dates of your issues and you set those manually. You can do that either by filling out those fields on your…

Hi @Caroline W_, That is because Jira Software is not installed or licensed in your instance. Have a look at this related question if it helps you on!