Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
  • Jimi Wikman
    Jimi Wikman

    Dependency and progress for roadmaps in Jira Software Cloud

    • Applauds 1
    • Interresting 1

    The roadmap feature in Jira Software Cloud's NextGen templates is getting a bit of an upgrade. In the new version we have two new features and soon we will get one of the features I am waiting for most.

    In this new update for Jira Software Cloud we get two new features. Dependencies allow you to quickly link two epics together to indicate that they are dependent on each other. This is a great feature that allow you to visualize dependencies in your timeline.

    The second feature is to indicate progress for child issues. This is shown below the epic name in the different status colors: grey, blue and green. This is not really as useful as if you could drill down on the items themselves in a hierarchy as you can in Portfolio for Jira. Still it is useful to quickly get a glance of the current status of things.

    Skärmavbild 2019-09-11 kl. 22.49.50.png

    In the next version we will see the addition of roadmap hierarchies. This will allow us to open up the child issues so we can see them in the tree. Unfortunately the child issues does not seem to be shown in the same way and in the first iteration we only seem to get this for one level of the tree. Sub-tasks will not be seen in the hierarchy as it looks right now.

    Roadmap hierarchies in roadmap for jira software cloud.jpeg

     

    I feel that this is a step in the right direction, but I am concerned about the fact that the road map feature only exist for Cloud users and even more so that it is only available for NextGen projects. The features are much wanted and if we can get a good transition of Portfolio for Jira to a simpler and more useful tool, then I think that will be a great selling point.

    For this to to be a replacement for Portfolio for Jira, which is positioned a bit between Jira Align and Roadmaps, then we need to be able to select what level we want to use and we need to be able to extend the parent child hierarchy with new levels. Using Epics in this way kind of annoy me since we are clearly working with features here rather than epics.

    It will be interesting to see if Roadmaps will remain a cloud only feature and how it will fit next to Jira Align and Portfolio for Jira in the future. For now I am enjoying the new feature and look forward to the next upgrade.

    Edited by Jimi Wikman


    • Applauds 1
    • Interresting 1


    User Feedback

    Recommended Comments



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By ©Jimi Wikman
      For users that have Atlassian Access or a Premium plan of Jira Software, Jira Service Desk, Jira Core, and Confluence a new feature have been released called Organization insights. In it's first iteration we get two charts that help us understand and predict product usage.
      The new feature called Organization insights is starting out with two charts, but more are coming. The idea behind Organization insights is to give insight into the usage of your products. These two charts can be used to:
      Identify adoption trends of specific products throughout your organization Understand and forecast product usage in the future Make data-driven decisions to increase usage in certain departments or use cases. Understand whether your license should be adjusted based on user activity Compare spending on various products against each other Quickly understand which users are inactive and should be deactivated.
       
       
       
       
      Organization Insights is available for Jira Software, Jira Service Desk, Jira Core, and Confluence  for anyone with a Premium plan or have Atlassian Access.  To access your organization's insights, you must be an organization admin. From your organization at admin.atlassian.com, select Security > Insights.
       
    • By ©Jimi Wikman
      Som så många andra älskar jag Jira Software Cloud på min iPhone och jag använder en webbläsare när jag jobbar på min Mac. Det kommer att ändras snart för Atlassian har annonserat på Apple’s Worldwide Developers Conference att Jira Software Cloud får en egen app till Mac senare i år!
      Förutom det faktum att Jira Software Cloud kommer att dra full nytta av macOS som notifieringar, keyboard shortcuts, spotlight sökningar, drag and drop, toolbars och så vidare, så kommer du även att synka mellan dina olika enheter.
      Jag ser fram emot att se mer av detta för att se exakt vad fördelarna kommer att bli över att köra den webbaserade varianten. Om du vill få en förhandsnotis när Jira Software Cloud kommer till App Store, då kan du registrera dig på Atlassians sida här.
    • By ©Jimi Wikman
      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
    • By ©Jimi Wikman
      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
    • By ©Jimi Wikman
      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?
×
×
  • Create New...