Search the Community

Priorities View File A simple icon set for Priorities I use in my own Jira instance. It uses colors to indicate priority / Severity ranging from full red in the blocker and then scale down in the color range down to purple for the lowest. The symbols are simplified as well to make them as visible as possible. Included: Blocker - Full red with a blocked icon as the indicator. Highest - 7 sided background in deep red with a white exclamation mark. High - Orange triangle pointing upwards. Medium - Green circle Low - Blue triangle pointing downwards. Lowest - Three purple dashes. Submitter ©Jimi Wikman Submitted 02/04/2020 Category Graphics

Regardless if you work in a continuous delivery flow like Kanban, a sequential delivery flow like waterfall or an iterative delivery flow like Scrum, you will benefit greatly from having portfolio management. Having a dedicated funnel ensures that you get a proper overlook of your incoming request. In this article we will discuss how that can be done by creating a process for it in Jira Software. Advanced Roadmaps is a very useful tool because it allows us to get the big picture. It also allows us to scale the hierarchies in Jira for issue types. This is important because the standard hierarchies are designed for teams, so they do not scale well. While you can work around this using the sideways approach where you have the higher hierarchies in a separate project and link between them, that is not really a hierarchy. This also works poorly when you wish to display things in Advanced Roadmap. The first thing we need to do for a proper hierarchy view in Advanced Roadmaps is to define the portfolio levels. We need to accommodate for multiple scenarios as requests, or demands, often come in different forms. The most common types are projects or even programs, or new features. We also want to make sure we can work with the different frameworks out there, so we add a collaboration level as well as defined in SAFe. To avoid a lot of confusion between different frameworks and other tools, we rename the Epic issue type in Jira Software to Feature. It will not be perfect, but it will have to do until we get the ability to rename it properly when Atlassian makes that change in the future. We do this by going to Issues -> Issue Types and edit the Epic issue type. We also add two new issue types for Initiative and Capability. Next we go to Plans -> Settings -> Advanced Roadmaps hierarchy configuration. There we add two new levels called Initiative and Capability and map them with our newly created issue types with the same names. Finally, we rename the Epic to Feature, and we should have our first hierarchy defined. We can go back and adjust this later if we want. The setup should now look like this: We can now add this to our projects by adding the issue types to our Issue Type Schemas. Depending on your setup you may want the new issue types for Initiative and Capability to exist in a separate Issue Type Schema, or you will add them to the standard schema. Either way we still need to give the new issue type a workflow that match their purpose. So we head over to Issues -> Workflows and create a new workflow. Again we want to consider what the purpose of these issue types is and who will actually work with them. Initiative, Capability and Feature are all used by management and requirement analysts to provide information on how to realize demands. That means that we do not have the same transfer of responsibility as for User Stories. Instead, we need to consider what we actually do in the portfolio and what we need to track in terms of activities. SAFe have a pretty good example of this for their Portfolio Kanban. Their first step is Funnel and for us that is pretty much everything that comes into our workflow, and we define this as new. Anything that comes in to the portfolio needs to be reviewed to see what we should focus on next. Since we will not review everything we add two steps for the review process: Ready for Review and In Review. This allows us to only pick things that we want to review by moving them from new to Ready for Review, and then we have an active status to indicate that we are working on this. We do the same for Analysis, which is the step where we involve Business Analysts and Requirement Analysts to define the need in more detail. For this we add Ready for Analysis for when the Review process lead to us spending time to break down the need in a requirement process. We also add the In Analysis to indicate that it has entered the Requirement process. Before we close this workflow we add the Implementation process as well. Ready for Implementation indicate that the requirement process has led to a decision to implement and In Implementation indicate that the need is being fulfilled. We do not fracture this further as we can easily drill down to individual tasks in Advanced Roadmaps, and it is not really useful to have for example test and release part of this workflow. That is because each issue type will have many issue types below it, and you can only transition on the last sub-task, making it misleading and feeling stagnant. Finally, we add a status for Blocked/Pending to allow us to track when things are preventing this activity from being fulfilled. This can be external or internal dependencies or financial reasons for example. As always we go for an open workflow to allow for free transitions. We add a close screen to the Close status to set a resolution and then add a post function to remove resolution on all other statuses. This workflow should now look like this: The final step is now to go to our workflow scheme and add this new workflow. We do this by going to Issues -> Workflow Schemes and click edit on the workflows scheme we have Initiative, Capability and Feature added to. We click add Workflow and add the new workflow we just created. Then we select that this workflow will be applied to Initiative, Capability and Feature before hitting save. This should now allow you to work inside Advanced Roadmaps using Initiatives, Capabilities and Features in a proper portfolio management process that allow for larger projects and programs as well as manage smaller feature or even user stories. I hope you found this useful and as always, if you have any questions just write a comment and I will do my best to help you. View full blog article

View full project

This is a repost from Atlassian's blog where the latest updates to the Atlassian cloud platform is posted. It is reposted here since the Atlassian blog does not have an RSS feed and so we can discuss the changes to the Atlassian Cloud architecture. You can follow these posts withe the tag "atlassian cloud changes". Atlassian Cloud Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management. See location details in the audit log The audit log has a new Location column that displays the IP address where the activity took place. Read more about audit logging. Email users with suggested account changes From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts. Give your users a Trusted permission From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves. Claim accounts after verifying a domain To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain. Set your language and time zone for Jira and Confluence in your Atlassian account profile Rather than individually setting your language and time zone in Jira and Confluence, these preferences will soon come from your Atlassian account profile. Visit your account preferences to update these settings. It may take up to 10 mins before your updated preferences are reflected in Jira and Confluence. Jira platform Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product. New user profile cards When you hover over someone’s name in directories, on dashboards, and in user picker fields, you’ll now start to see rich profile cards with more information and a link to the user’s profile (if you have permission to see it). Next-gen: Epic panel in backlog You can now manage epics on the backlog of your next-gen project via the Epics panel, similar to how epic management works in classic Jira Software projects. Changes you make in the panel on the backlog will reflect on the Roadmap, and vice-versa. Having trouble with next-gen projects? Better help is here. We improved our in-product help experience. Try the Help button in the navigation bar to see help articles related to your next-gen project or service desk. Advanced search (JQL): Search for content updated by a specific user Use the updatedBy() function to search for issues that were updated by a specific user, optionally within the specified time range. For example, if you want to find issues updated by John Smith between June and September 2018, enter issuekey IN updatedBy(jsmith, "2018/06/01", "2018/08/31"). Read more about the updatedBy() function. Portfolio for Jira - Scheduling Team Sorting When scheduling work, Portfolio now prioritizes teams that have associated issue sources over teams that don't. Also, teams without issue sources will only be considered if they have capacity to complete work earlier. Jira Software We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects. Enforce CSFR protection on Agile 2.0 mutations If a user attempts to perform any JSW create/update action with a stale Xsrf token, they will be presented with an error flag with a message: Our session has expired Refresh the page and try again GitHub app on the Atlassian Marketplace We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet. This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector. Next-gen: Roadmap issue hierarchy You can now expand an epic on your roadmap to see its child issues and their statuses. Learn more about managing epics on the roadmap. Next-gen: Create child issues on your roadmap You can now add child issues directly on your roadmap. Just hover over an epic, click the + icon, and give your issue a name. Learn more about managing epics on the roadmap. Next-gen: Environment system field in JSW Add Jira’s built-in Environment field to your issue types in next-gen projects. In your project, go to Project settings > Issue types and drag the Environment field into the Description section of the issue layout. Jira Service Desk Automatically clear the value of a request's field when changing its status in your next-gen service desk We improved our “Update a request field” workflow rule. Now, you can use the rule to clear your request’s fields when someone moves the request using a specific transition. New issue view for Jira Service Desk The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view. Use keyboard shortcuts in your queues Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard! Customer portal request details page redesign We have redesigned the customer portal request details page to make it easier to use. You’ll notice we have added a rich text editor, sorted the activity stream from old to new, and have moved the location of the request fields, share button, approval and comment boxes. Maintenance complete on the customer portal user profile page We have just completed some maintenance on the customer portal user profile page. We also introduced a new layout that is easier to use on mobile devices. Go team! Easier configuration for the new issue view If you have the new issue view, you can now easily configure how your issue view looks for each request type. From your service desk project, go to Project settings > Request types and you'll find the new layout for making changes. Global create can select request type and raise on behalf of You can now create a request on behalf of your customers and set them as the reporter. Use the global create button ( + ), then select Raise this request on behalf of and add in your customer's email. Confluence Convert legacy editor pages to the new editor Our goal is to allow you to convert your pages from the legacy editor to the new editor without data loss and with little to no changes to the look and feel of the content, which is why you’ll have control over which pages get converted and when. You'll also have the option to preview any page before converting it. We want you to feel comfortable with the process. You'll also have the chance to restore a page to its previous, legacy editor version after conversion. Learn more Your editing experience just got an upgrade The new Confluence editor allows anyone to create beautiful, powerful pages effortlessly. Check out the editor roadmap to learn more. We're extending editing improvements to all pages on Android The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site. Annotate images in the new editor Annotate images by adding text, inserting shapes and lines, using brushes, or adding a blur to a certain area. Confluence Cloud recent pages drawer We’ve made it easier to get to the pages you visited or worked with most recently. A new action has been added to the global sidebar that presents you with a list of your recent pages; interaction-specific tabs help you narrow the list based on your actions, like visited, edited, or saved as draft. Share pages directly with your team It’s now easier to share pages with everyone on your team, all in one go. When you click Share on any page or blog post, Confluence now lets you add a team – no need to enter each person individually. Learn more Jira issue URLs are converted to smart links When you paste a Jira issue link into a Confluence page, the URL is converted to a smart link that displays the page icon and the page title. This works if the Jira and Confluence sites are linked or if they are both cloud versions. Convert pages to use the new editor You can now convert your existing pages that were created using the legacy editor to use the new editing experience! Learn more Confluence navigation just got better Get to information faster with improved navigation – making what you need visible from anywhere in Confluence. Learn more Align and resize images in tables in the new editor When images are inserted in table cells, you now have the ability to align and resize them. Portfolio for Jira plan macro The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams. Improved expand element replaces the macro Content creators just got a better way to control the way information is presented. The existing expand macro has been replaced with a quicker, easier way to include the expand functionality. Insert the improved expand element using /expand or by inserting the element from the editor's Insert toolbar. Bitbucket New Code Review - Limit the amount of rendered diff content Limits the amount of pull request content rendered in the diff and file tree to improve browser performance. Limits include the overall # of files and # of lines for the entire diff. Learn more View full blog article

This is a repost from Atlassian's blog where the latest updates to the Atlassian cloud platform is posted. It is reposted here since the Atlassian blog does not have an RSS feed and so we can discuss the changes to the Atlassian Cloud architecture. You can follow these posts withe the tag "atlassian cloud changes". Atlassian Cloud Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management. Email users with suggested account changes From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts. Give your users a Trusted permission From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves. Claim accounts after verifying a domain To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain. Set your language and time zone for Jira and Confluence in your Atlassian account profile Rather than individually setting your language and time zone in Jira and Confluence, these preferences will soon come from your Atlassian account profile. Visit your account preferences to update these settings. It may take up to 10 mins before your updated preferences are reflected in Jira and Confluence. Jira platform Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product. New issue view: Print an issue or export it to Microsoft Word or XML Print or export individual issues in the new issue view. Open an issue and choose more actions (•••) at the top-right to print it or export it to Microsoft Word (DOC) or XML format. Changing the "Issues and filters" navigation item to "Filters" In preparation for the rollout of our improved navigation for Jira Cloud, we've updated the "Issues and filters" menu item in the Jira sidebar to simply be "Filters." When we move to the new horizontal navigation, this name will better reflect what you'll find in the menu—filters, filters, and more filters. This is purely a label change at this point, and won't change any functionality. New user profile cards When you hover over someone’s name in directories, on dashboards, and in user picker fields, you’ll now start to see rich profile cards with more information and a link to the user’s profile (if you have permission to see it). Next-gen: Epic panel in backlog You can now manage epics on the backlog of your next-gen project via the Epics panel, similar to how epic management works in classic Jira Software projects. Changes you make in the panel on the backlog will reflect on the Roadmap, and vice-versa. Advanced search (JQL): Search for content updated by a specific user Use the updatedBy() function to search for issues that were updated by a specific user, optionally within the specified time range. For example, if you want to find issues updated by John Smith between June and September 2018, enter issuekey IN updatedBy(jsmith, "2018/06/01", "2018/08/31"). Read more about the updatedBy() function. Jira Software We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects. GitHub app on the Atlassian Marketplace We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet. This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector. Next-gen: Roadmap issue hierarchy You can now expand an epic on your roadmap to see its child issues and their statuses. Learn more about managing epics on the roadmap. Next-gen: Create child issues on your roadmap You can now add child issues directly on your roadmap. Just hover over an epic, click the + icon, and give your issue a name. Learn more about managing epics on the roadmap. Next-gen: Environment system field in JSW Add Jira’s built-in Environment field to your issue types in next-gen projects. In your project, go to Project settings > Issue types and drag the Environment field into the Description section of the issue layout. Jira Service Desk New issue view for Jira Service Desk The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view. Use keyboard shortcuts in your queues Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard! Customer portal request details page redesign We have redesigned the customer portal request details page to make it easier to use. You’ll notice we have added a rich text editor, sorted the activity stream from old to new, and have moved the location of the request fields, share button, approval and comment boxes. Maintenance complete on the customer portal user profile page We have just completed some maintenance on the customer portal user profile page. We also introduced a new layout that is easier to use on mobile devices. Go team! Easier configuration for the new issue view If you have the new issue view, you can now easily configure how your issue view looks for each request type. From your service desk project, go to Project settings > Request types and you'll find the new layout for making changes. Next-gen projects: Approve or decline requests You can now add an approval stage to requests that should be approved before they’re resolved in next-gen projects. If a request has an approval stage, approvers can approve or decline the request from the issue view. Add an approval stage to a workflow by going to Project settings > Request types and then clicking Edit workflow. Learn more Global create can select request type and raise on behalf of You can now create a request on behalf of your customers and set them as the reporter. Use the global create button ( + ), then select Raise this request on behalf of and add in your customer's email. Introducing multi-line fields to the issue view in next-gen projects You can now add multi-line fields to the issue view. These fields communicate long-form information to your team members and aren’t visible to your customers. To add multi-line fields, go to Project settings > Request types and add fields to the Description fields bucket. Confluence Your editing experience just got an upgrade The new Confluence editor allows anyone to create beautiful, powerful pages effortlessly. Check out the editor roadmap to learn more. We're extending editing improvements to all pages on Android The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site. Annotate images in the new editor Annotate images by adding text, inserting shapes and lines, using brushes, or adding a blur to a certain area. Confluence Cloud recent pages drawer We’ve made it easier to get to the pages you visited or worked with most recently. A new action has been added to the global sidebar that presents you with a list of your recent pages; interaction-specific tabs help you narrow the list based on your actions, like visited, edited, or saved as draft. Share pages directly with your team It’s now easier to share pages with everyone on your team, all in one go. When you click Share on any page or blog post, Confluence now lets you add a team – no need to enter each person individually. Learn more Jira issue URLs are converted to smart links When you paste a Jira issue link into a Confluence page, the URL is converted to a smart link that displays the page icon and the page title. This works if the Jira and Confluence sites are linked or if they are both cloud versions. Convert pages to use the new editor You can now convert your existing pages that were created using the legacy editor to use the new editing experience! Learn more Confluence navigation just got better Get to information faster with improved navigation – making what you need visible from anywhere in Confluence. Learn more Align and resize images in tables in the new editor When images are inserted in table cells, you now have the ability to align and resize them. Portfolio for Jira plan macro The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams. Improved expand element replaces the macro Content creators just got a better way to control the way information is presented. The existing expand macro has been replaced with a quicker, easier way to include the expand functionality. Insert the improved expand element using /expand or by inserting the element from the editor's Insert toolbar. Bitbucket New Code Review - Limit the amount of rendered diff content Limits the amount of pull request content rendered in the diff and file tree to improve browser performance. Limits include the overall # of files and # of lines for the entire diff. Learn more View full blog article

This is a repost from Atlassian's blog where the latest updates to the Atlassian cloud platform is posted. It is reposted here since the Atlassian blog does not have an RSS feed and so we can discuss the changes to the Atlassian Cloud architecture. You can follow these posts withe the tag "atlassian cloud changes". Atlassian Cloud Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management. Email users with suggested account changes Rolling Out From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts. Give your users a Trusted permission From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves. Claim accounts after verifying a domain To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain. Set your language and time zone for Jira and Confluence in your Atlassian account profile Rather than individually setting your language and time zone in Jira and Confluence, these preferences will soon come from your Atlassian account profile. Visit your account preferences to update these settings. It may take up to 10 mins before your updated preferences are reflected in Jira and Confluence. Jira platform Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product. New user profile cards When you hover over someone’s name in directories, on dashboards, and in user picker fields, you’ll now start to see rich profile cards with more information and a link to the user’s profile (if you have permission to see it). Next-gen: Epic panel in backlog You can now manage epics on the backlog of your next-gen project via the Epics panel, similar to how epic management works in classic Jira Software projects. Changes you make in the panel on the backlog will reflect on the Roadmap, and vice-versa. Advanced search (JQL): Search for content updated by a specific user Use the updatedBy() function to search for issues that were updated by a specific user, optionally within the specified time range. For example, if you want to find issues updated by John Smith between June and September 2018, enter issuekey IN updatedBy(jsmith, "2018/06/01", "2018/08/31"). Read more about the updatedBy() function. Search for and filter projects by their type with the "projectType" JQL field We added a new JQL field to search for and filter projects by their type. Type projectType to filter “software” (Jira Software) projects, “service_desk” (Jira Service Desk) projects, “business” (Jira Core) projects, or “ops” (Jira Ops) projects. Jira Software We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects. GitHub app on the Atlassian Marketplace We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet. This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector. Next-gen: Roadmap issue hierarchy You can now expand an epic on your roadmap to see its child issues and their statuses. Learn more about managing epics on the roadmap. Next-gen: Create child issues on your roadmap You can now add child issues directly on your roadmap. Just hover over an epic, click the + icon, and give your issue a name. Learn more about managing epics on the roadmap. Next-gen: Add the Environment field to issues Add Jira’s built-in Environment field to your issue types in next-gen projects. In your project, go to Project settings > Issue types and drag the Environment field into the Description section of the issue layout. Large backlogs load faster Big backlogs can take time to load, and teams usually work with a small chunk of the issues at a time. Knowing this and striving to make backlogs render faster, we've changed the default to display only 100 issues (90 from the top and 10 from the bottom) from your backlog. The remaining issues will be displayed if you click Show all issues. We've also introduced a number of backend changes that resulted in faster initial loading. Jira Service Desk Issues with the customer organizations field now use the organization name instead of ID when exporting to CSV When exporting Jira issues to CSV from the Jira Issue Navigator, the Custom field (Organizations) now contains the name of the organizations linked to the issue. The field previously contained the organization ID, which was not valuable for exports used for reporting. As part of this change, a CSV import can now match organizations by both their ID and their name. No changes are needed if you use CSV export files for import. New issue view for Jira Service Desk The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view. Use keyboard shortcuts in your queues Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard! Customer portal request details page redesign We have redesigned the customer portal request details page to make it easier to use. You’ll notice we have added a rich text editor, sorted the activity stream from old to new, and have moved the location of the request fields, share button, approval and comment boxes. Maintenance complete on the customer portal user profile page We have just completed some maintenance on the customer portal user profile page. We also introduced a new layout that is easier to use on mobile devices. Go team! Easier configuration for the new issue view If you have the new issue view, you can now easily configure how your issue view looks for each request type. From your service desk project, go to Project settings > Request types and you'll find the new layout for making changes. Global create can select request type and raise on behalf of You can now create a request on behalf of your customers and set them as the reporter. Use the global create button ( + ), then select Raise this request on behalf of and add in your customer's email. Confluence Your editing experience just got an upgrade The new Confluence editor allows anyone to create beautiful, powerful pages effortlessly. Check out the editor roadmap to learn more. We're extending editing improvements to all pages on Android The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site. Annotate images in the new editor Annotate images by adding text, inserting shapes and lines, using brushes, or adding a blur to a certain area. Confluence Cloud recent pages drawer We’ve made it easier to get to the pages you visited or worked with most recently. A new action has been added to the global sidebar that presents you with a list of your recent pages; interaction-specific tabs help you narrow the list based on your actions, like visited, edited, or saved as draft. Share pages directly with your team It’s now easier to share pages with everyone on your team, all in one go. When you click Share on any page or blog post, Confluence now lets you add a team – no need to enter each person individually. Learn more Jira issue URLs are converted to smart links When you paste a Jira issue link into a Confluence page, the URL is converted to a smart link that displays the page icon and the page title. This works if the Jira and Confluence sites are linked or if they are both cloud versions. Convert pages to use the new editor You can now convert your existing pages that were created using the legacy editor to use the new editing experience! Learn more Confluence navigation just got better Get to information faster with improved navigation – making what you need visible from anywhere in Confluence. Learn more Align and resize images in tables in the new editor When images are inserted in table cells, you now have the ability to align and resize them. Portfolio for Jira plan macro The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams. Improved expand element replaces the macro Content creators just got a better way to control the way information is presented. The existing expand macro has been replaced with a quicker, easier way to include the expand functionality. Insert the improved expand element using /expand or by inserting the element from the editor's Insert toolbar. View full blog article

The Roadmap feature in Jira Cloud's NextGen projects is getting three new features. While all good additions, the question still remain who these new features are for and to what extent these new features will make people move over to NextGen projects. NextGen for Jira Cloud is in a strange place as it is not really defined what is can and should be used for. The Roadmap feature is in a similar place as it fall somewhere between Portfolio for Jira and the Roadmap planner macro in Confluence. These 3 new features are an improvement and a good indication on where Atlassian are going. The question is just how fast these new features are coming out and if it appeal to the target audience. Drill down into the details The first feature is the ability to open up the Epic and see the underlying tasks. This is a much needed feature that was heavily requested and also one I spoke with Atlassian about earlier this fall. This is a good feature and a good step to improve the roadmap, but is still in need of further refinement. We still only have Epics as the starting point, which will limit the use of Roadmaps. Opening up the subtasks will only show their status at the moment, which is useful, but not what many want. Many still want a Gant view where the sum of the subtasks should make up the time in the Epic. This is not possible at the moment and I find it interesting that Atlassian has chosen to follow an Agile first approach to the Roadmaps, which means it will not be very useful for the majority of the companies using Atlassian's products today. Add new tasks directly in the Roadmap Another great feature that was much requested is the ability to create new sub tasks directly in the Roadmap. This way we can build up a full stack of tasks for a project in one view, which is excellent for portfolio and project planning purposes. The fact that we do not get full Gantt view for the sub tasks makes this a little less useful for time and resource planning however. Filter your Epics and Tasks The ability to use different filters is a must for any Portfolio, but even roadmaps benefit from filtering options. In this release we get the filters for issue status and assignee, which is a good start. I would like to see some more filters like dependencies and of course issues that are behind the time schedule. The question is just who this Roadmap feature is for though as then we are moving more into project management and Portfolio management and Atlassian has previously stated that the Roadmap is for teams. It's a good start, but... I am still not sure where NextGen projects are heading, which means it's hard to say if the features are great or poor. We know that Roadmaps will be ported over to the Classic project types as well, but that will make things even more confusing. This is unfortunately a common issue with Atlassian as they are getting more and more fractured with no clear indication on structure or strategy. Roadmaps for me is something that should stay as a team tool for small teams to give an overview of the current work. To cater to that need Roadmaps could benefit from a few changes. The first would be to change the basic structure and allow the view to be in any level. That means that I should be able to use Stories rather than Epics as Epics are just containers and not work tasks. The majority of issues are not connected to Epics in most teams, especially if you work in a Kanban setting for continuous improvements for example. The second would be to go full gantt, or rather to give the option to go full gantt. Not every team need or will use estimation in issues, but most do. Without a full gantt the view of issues will not be as useful as a progress overview tool. It's like saying that I have a container of a certain size and in that container I have put five items. On the question if the items will fit my only answerr will be "I don't know", which is in many organizations not an acceptable answer. The third would be to add dependencies on issues and not just on Epics and extend the data to also show data from other projects. In most organizations dependencies are not within the team itself, but to surrounding teams. Even if the view is for the team it makes sense that I should be able to see what other teams could be affected. The fourth would be to ensure that Roadmaps becomes a granular part of a larger view. Right now it is an isolated feature, which means that we will have different data for different levels of the organization. This will lead to miscommunication within the organization as teams will say Epics, which will mean something very different to Program managers and Portfolio managers and so on. As more and more organization add SAFe to their processes it is important that the team view is part of the greater whole. I am sure we will so many great additions to Roadmaps in 2020 and hopefully many of the questions we have regarding Roadmaps and NextGen projects will get answers then. Until then these three new features are welcome additions that I am sure will help many teams improve their work processes. View full blog article

Atlassian Cloud Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management. Email users with suggested account changes ROLLING OUT From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts. Give your users a Trusted permission ROLLING OUT From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves. Claim accounts after verifying a domain ROLLING OUT To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain. Jira platform Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product. New user profile cards ROLLING OUT When you hover over someone’s name in directories, on dashboards, and in user picker fields, you’ll now start to see rich profile cards with more information and a link to the user’s profile (if you have permission to see it). New issue view: Rich user profile cards ROLLING OUT Get to know your team even faster. Our new user profile card provides more user information and a link to the user’s profile (if you have permission to see it). You’ll see it when you hover over someone’s name in user-picker fields (assignee, reporter, and other custom fields) and in issue activity feeds (comments, history, and the work log). Jira Software We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects. New issue view for Jira Software ROLLING OUT Get a consistent view and edit experience with our new issue view for Jira Software. Click an issue to see its details, edit any field with a click, and add content with the quick-add buttons (under the issue summary). Take a look at the documentation for more info. We're adding new features and refining the design all the time, so click Give feedback on the issue view to let us know what you think. GitHub app on the Atlassian Marketplace ROLLING OUT We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet. This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector. Jira Service Desk Issues with the customer organizations field now use the organization name instead of ID when exporting to CSV ROLLING OUT NEW THIS WEEK When exporting Jira issues to CSV from the Jira Issue Navigator, the Custom field (Organizations) now contains the name of the organizations linked to the issue. The field previously contained the organization ID, which was not valuable for exports used for reporting. As part of this change, a CSV import can now match organizations by both their ID and their name. No changes are needed if you use CSV export files for import. Maintenance complete on the Request and Approvals pages ROLLING OUT NEW THIS WEEK We've completed some maintenance to the customer portal, you may notice some cosmetic updates to the Request and Approvals pages. New issue view for Jira Service Desk ROLLING OUT The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view. Use keyboard shortcuts in your queues ROLLING OUT Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard! Customer portal request details page redesign ROLLING OUT We have redesigned the customer portal request details page to make it easier to use. You’ll notice we have added a rich text editor, sorted the activity stream from old to new, and have moved the location of the request fields, share button, approval and comment boxes. Easier configuration for the new issue view ROLLING OUT If you have the new issue view, you can now easily configure how your issue view looks for each request type. From your service desk project, go to Project settings > Request types and you'll find the new layout for making changes. Improved interface for your customer portal settings ROLLING OUT We’ve given the customer portal page in your project settings a visual overhaul. Settings are under suitable headings, text sizes are aligned, and overall, the page has a cleaner interface. Don’t worry, we haven’t removed any functionality. To see the new design in a classic project, go to Project settings > Portal settings. To see the new design in a next-gen project, go to Project settings > Channels > Customer portal. Confluence Portfolio for Jira plan macro ROLLING OUT NEW THIS WEEK The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams. Blogs are getting the first round of editing improvements ROLLING OUT If you've ever thought 'I wish it was easier to read blogs on mobile.... or on other devices', then this change is for you. Blogs are getting fixed-width layouts to improve readability across all devices. We're making a bunch of other updates to improve editing reliability and clean up your editing experience, so some macros may be temporarily unavailable while they're under maintenance. You can read more about these changes on our docs site. Teams have arrived in Confluence retrospectives! ROLLING OUT Instead of having to individually add each member of your team to a retrospective, Confluence now lets you assign people to Teams, so you can bulk add everyone at once. Use the retrospective template to see Teams in action. You can edit Teams through the retrospective-creation process, and add or edit other attendees for each retrospective you create. We're extending editing improvements to all pages on Android ROLLING OUT The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site. Confluence Cloud recent pages drawer ROLLING OUT We’ve made it easier to get to the pages you visited or worked with most recently. A new action has been added to the global sidebar that presents you with a list of your recent pages; interaction-specific tabs help you narrow the list based on your actions, like visited, edited, or saved as draft. Share pages directly with your team ROLLING OUT It’s now easier to share pages with everyone on your team, all in one go. When you click Share on any page or blog post, Confluence now lets you add a team – no need to enter each person individually. Learn more Bitbucket Retarget stacked Pull Requests ROLLING OUT NEW THIS WEEK Bitbucket will retarget the dependent pull requests to the branch that you're merging into, before closing the branch of the pull request you're merging. Previously, if there were dependent pull requests, you needed to update them manually with the new target branch. You will now see a checkbox with a link to the affected pull requests that will be retargeted. View full blog article

Atlassian has announced that a free tier for all of the company’s services that didn’t already offer one is coming. Atlassian now also offers discounted cloud pricing for academic institutions and nonprofit organizations. This is great for smaller companies that want to upgrade from the popular Trello platform, which is also owned by Atlassian. Jira Software, Confluence, Jira Service Desk and Jira Core will get free tiers in the coming months. Exactly what the limits will be on these free tiers is yet to be seen, but it is safe to assume that the current 10 user tier that is the entry level will probably be free. In addition to this we will also see an extension of the trial version which is very short today. This allow companies to better evaluate before committing to a purchase. "We’re announcing free plans of Jira Software, Confluence, Jira Service Desk, and Jira Core – available in the coming months. This adds to the existing free offerings already in place for Trello, Bitbucket, and Opsgenie to give teams of all sizes, even small ones, a set of fundamental capabilities for team collaboration." - Reaching new heights in the cloud For me this is great news as it allow many smaller companies to get introduced to Jira. This allow Jira to organically become a foundation of the workflow as the companies grow. This should multiply the use of Jira quite a bit, especially with the new next-gen features that are very similar to Trello. I like this move quite a bit and I look forward to hearing more about this as the new tiers are published. In addition to this they also talk about their Cloud Premium offer and the new discount offer for academic and non-profit organizations. View full blog article