Search the Community
Showing results for tags 'jira cloud'.
Found 2 results
In the coming months we will see some changes to the navigation in Jira and Confluence for the cloud versions. This after a round of feedback was done in July this year on the new experience. This change will roll out slowly and you can delay the change if you need time to prepare the users for the change. There has been some negative feedback regarding the current navigation in Jira and Confluence cloud as it is a bit difficult to use. This is why a new experience was designed and tested during the summer by 350+ users. The feedback on the new navigation was positive and so now it is going live to cloud users in a slow rollout. This is a rollback to the old navigation experience which is good as it will make the transition from Server and DC versions easier. I like the new apps and people sections in the navigation as well. That should make it easier to group things to keep navigation organized. The fact that Jira and Confluence now get a uniform navigation is also excellent. On the documentation page for the new Confluence navigation we find more details on the new navigation and it's design. App switcher - Switch to other Atlassian Cloud apps, like Jira, and go to recent Confluence spaces and Jira projects. Confluence logo and name - Click this to go to the Confluence Home page. Home - Begin your Confluence journey and reorient yourself when you’re moving on to a new piece of work by easily accessing the spaces, pages, and updates that are important to you. Recent - Access pages you’ve recently visited and worked on as well as pages saved as draft or starred. Spaces - Get to spaces you’ve recently visited and starred. People - Search for people on your site by visiting the people directory. Apps - Access content from apps like Analytics, Calendars for Confluence, or Questions for Confluence. Create - Click to create a new page, either blank or from a template. Search - Find pages, spaces, and other content. Notifications - Find out what's happening in Confluence and other Atlassian apps, like Jira. Help - Get online help, and find out what's new in your Atlassian Cloud apps. Your profile and settings - Go to or create your personal space, find out about the new Confluence experience, and adjust your Confluence settings. New Homepage In addition to the new navigation we will also get a new start page, or home page as it is called. This will appear in both Jira and Confluence cloud at the same time as we will see the new navigation. For Confluence it will give an overview over: Spaces - Get back to the spaces you care about, starred or recently visited Recent pages - Find pages you’ve drafted, recently published, visited, or starred All updates - View the updates across your site The Home page for Jira follow that principle, but is a bit slimmed down. I think there are more things that can go in this view and I hope we will see the same structure as for Confluence in the future. So instead of spaces we would have projects and then I would like to have a list of favorite boards somewhere.
Atlassian is continuing to push for their cloud services and many new and innovative features for Jira Cloud are added to the new next-gen project type. This is the most open and flexible project type ever created for Jira cloud, which can cause serious headache for large organizations. "In next-gen, projects are entirely independent from one another, meaning you can change something in one project and it won’t impact anything in another. In next-gen, workflows live within projects and will be tied to specific issue types. So for example you could have a specific workflow for your bugs and another workflow for your stories. Because the projects are entirely independent from one another, it gives teams more autonomy to adjust and continuously optimize their workflows without impacting other teams or having to bother administrators." - NextGen roadmap The total freedom to create your own workflows and customize the way you work is a dream come true for many project owners. For method and process offices however they are a nightmare unless you are one of the few enterprise companies that actually work with work processes in Jira on a daily basis. Many of the companies I meet struggle to even maintain a common way of working with a strict workflow policy. The idea of letting every project getting the power to create their own way of working could be a nightmare for those companies. So what can you do to control the way of working so people can work cross projects and still allow for freedom and autonomy within the projects? I believe in education and freedom under responsibility. That being said I think that next-gen should not be treated any different than Jira in general. If you have a defined way of working, and I do not mean what words you should use based on methodology, but an actual way of working. Then teach the users. As long as the way of working makes sense to the users, then they will naturally follow it. You also need coaches to support the teams. This is important, not just because we want to give the teams the best possible chance to succeed, but also so we can capture new ideas and improvements to the way of working. This way we can continuously improve the way we work together. If there is one change I would like to see in large organizations, then it is to have a proper center for way of working: The WOW office. Many have similar offices, but they almost always follow a top-down approach where they focus on processes and methods. The concept of defining a method rather than asking the users how they want to work is for me a complete waste of time. I see so many companies focusing on defining words instead of describing what is actually done. So I would suggest a bottom-up approach with each capability having it's own organizations. If you have proper support for the teams and you have a healthy WOW office that can train the teams on how to use the tools in your organization, then you are going to have a great time. If you on the other side do not have a WOW office with a defined way of working that is aligned with the users or a support organization to train and support the teams....then do not allow the creation of next-gen projects in your organization. Next-gen projects have the potential to fracture your organization, or form mega projects with thousands of users. It can form barriers making working cross projects impossible and lead to customizations that will quickly make life hard for everyone. This is the same issue many organizations face when they have a loose policy for customizations, but with next-gen projects you will loose any possibility to control the way each and every project will define their work processes. With the push from Atlassian towards Cloud and the changes to licensing models for large organizations this is not something you need to look at in the future. This is a reality now and you better prepare for it before you end up in a bad situation. Next-gen projects is the future. With right preparation and investment I think it will supercharge your teams to a productivity and creativity that you have never seen before. Make sure you have a plan for it and how to align all that power to a common way of working without crippling the teams autonomy. Are you prepared?