Jump to content
  • Jimi Wikman
    Jimi Wikman

    Atlassian Cloud changes Nov 4 to Nov 11, 2019

    • Interresting 1

    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.


    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).


    New issue view: Rich user profile cards


    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


    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


    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


    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


    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


    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.


    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.


    Improved interface for your customer portal settings


    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.



    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.


    Blogs are getting the first round of editing improvements


    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!


    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


    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


    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



    Retarget stacked Pull Requests


    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.

    User Feedback

    Recommended Comments

    There are no comments to display.

    Join the conversation

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

    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
      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.

    • By ©Jimi Wikman
      Confluence cloud get some new features for the comments in the coming weeks. It includes quick commands and access to more macros. My question however is if we actually need this or if comments in general need a different approach?
      "Comments are where important discussions happen inside Confluence. Feedback and questions in page comments shape ideas and keep work moving forward. We've dedicated a lot of time to improving the experience, because we know comments are important to our customers and their team collaboration. The new experience is meant to help your teams better express themselves and have meaningful conversations."
      In my experience comments in Confluence is not really used as much as I think Atlassian believe. Mostly this is because inline commenting is often more efficient or because commenting is used less due to direct communication. So adding more features to the commenting part of the Confluence experience does seem a bit unnecessary.
      One concern I have about bloating the comment section is that we will see it used instead of editing the pages properly. I have seen in in other areas where it become easier to just add comments than actually use the proper way to document. Adding more functions also have the risk of making the comment section harder to use. Just adding large images and tables with data makes this area quite messy.
      Still, I like the "/" command that is very similar to the one used by Notion and having the option to use comments in a more powerful way is not necessarily a bad thing. Interestingly enough the news met with several questions on when comments will be available in edit mode, which seem to be a more requested feature at the moment...

    • By ©Jimi Wikman
      Notion.so is a relatively new product, but it is already making some waves and is often mentioned in comparison with Atlassians products. At first glance it has a good spread of functionality and a price that can really challenge the Atlassian giant, especially for small to medium companies.
      "Write, plan, collaborate, and get organized. Notion is all you need — in one tool."
      Notion.so started in 2016 in San Fransisco and it has already attracted many users to its simple, yet powerful features. On their website they have 4 areas that they see as their core: Notes & docs, Knowledge base, Tasks & Projects and Database. If we compare these with the Atlassian suite it is pretty much Confluence with Trello baked into one product.
      The editing capabilities are not bad and Notion.so uses an inline editing function rather then the old click to edit function in Confluence. It is very nice and uses the "/" command to access the functions rather than a toolbar. The permissions system is a bit different, but seem pretty solid from what I can tell. Once you get the hang of things it is very, very easy to build content with Notion.so.
      The capabilities for Tasks & Projects are very similar to Trello so if you know how to work with Trello you should have no issues with Notion.so. If anything I feel that Notion.so actually have a more capable feature set than Trello by allowing a ton of fields that can be customized to create some pretty sophisticated setups. While not nearly as powerful as Jira for development purposes, this is is more than enough for many other situations.

      Databases follow pretty much the same capabilities as for tasks and pages. In fact tasks comes from a database by default. This means that you can create pretty awesome databases with multiple views, including tasks, lists and even a calendar view. Personally I love the feature that each row in my table can be edited as a separate page.
      At a very affordable price compared to Confluence and Jira with pretty solid features this is not a bad alternative. There are some concerns regarding security as Notion.so do not have any ISO, SOC 2, HIPAA certificates, but considering they have passed reviews from companies such as Slack and Intercom that is probably not a big thing for it's user base.
      I see Notion.so as a good alternative for small to medium non-development companies. It can work for smaller development companies as well as for large non-development companies, but I think the sweet spot is in the small to medium non-development area. The price also suggest that as it is user based and at the top tier with 20 dollars per user it is getting pretty expensive.

      I like Notion.so and I think it definitely have a place in some organizations. It is clearly being developed with passion where the goal is not to make money, but to make people's life easier and more organized. As always they get an extra gold star for giving students and educators this awesome product for free.
      Notion.so comes as an online cloud solution, a mobile app as well as downloads for mac and windows that even allow offline editing....and did I mention it has a dark mode that is simply amazing?
      If you have not tried it, then go and sign up for a free account today and give it a go.
    • By ©Jimi Wikman
      In the previous article we discussed what tools we should use for what purpose. Now it's time to define the work we want to do in the different Areas of Responsibility. We do that by defining what different type of work we do in each so we can create a separate issue type for each type of work. This way we can separate work and can evolve the way we work in each through fields and workflows for example. Before we dig into that however we should first identify what issue types really are and how we should use them properly.
      The three levels of issues in Jira
      In Jira we have 3 levels of issue types. Each level is used for different purposes so it is important to understand what that purpose is so we can map our issue types to the right level.
      Epic - This is the highest level in Jira and it's purpose is to group and categorize the lower levels. In itself an Epic has no value and you can see it as a box or a rubber band that simply is used to group other items. The term epic means a story that extends over a long period of time or that it is something grand and impressive. This is also how it is meant to be used in Jira as a way to mark stories that are connected and span over two or more time periods.
        Standard Issue Type - This is the middle level in Jira and it's purpose if to act as the transitional item to indicate what responsibility area currently own the responsibility to do something. This type is the one that we design workflows for that are flow chart based and not in the form of state diagrams. We will cover this when going over workflows in a later article.
        Sub-Tasks - Within each responsibility area we have a need to break down the work so we can mark them as complete. These are referred to as producing items and unlike the Standard Issue Type we do not always use a tranistional workflow, but more of a task management flow of open, in progress, done .We will cover this when going over workflows in a later article. The majority of our issue types will fall into this category.
        Identifying the work that need to be done
      With the issue types identified we can now begin to define what issue types we need for our setup. We previously identified Requirement, Development, Test and Acceptance as our areas that use Confluence and Jira, so we will break down the work in those areas and see what we can come up with.
      Requirement: Standard Issue Type (optional) - If we want, we can use a separate issue type to act as the object which we work through the requirement process. This should be done in a separate project as it will contain a large number of unprocessed need. This would make managing the development projects less efficient, but we will discuss that in another article.
        Story: Standard Issue Type - This is the output from the Requirement process and while the name might make you think it comes from the fact that many requirements are written in the form or user stories. This is not accurate however as requirements can come in many forms and shapes. Story refer to the fact that we get the need explained to us as a story, which is because as humans we communicate in the form of stories.
        Design: Standard Issue Type & Sub-task - Design (UX/UI) can be done separate, which is why we have a Standard Issue Type for it. It can also be done as part of a requirement which is why we have a sub-task for it as well. In some cases we need to make adjustments in existing requirements and there we also use a sub-task connected to a Story for that purpose.
        Technical Design: Standard Issue Type & Sub-task - Just like with Design we have both a standard issue type and a sub-task.
        Technical Debt: Standard Issue Type - This is a rare issue type in many companies, but it is used when decisions are made that create technical debt or when clean up need to be done to optimize systems and data. These are IT driven stories in nature with the intent to make sure IT driven concerns are logged and prioritized alongside business need. It is also used to highlight decisions that will have a cost in the future. Development
      Development: Sub-Task - It may seem strange that Development only exist as sub-task, but the reason for that is that development only happen when there is a need for it. This need is in the form of a Story or Technical debt. That is why development only exist as a sub-task and it is used for writing code.
        Build & Configure: Sub-task - Again this is only available as a sub-task for the same reason as for Development. This issue type is used when there is no code related to the task, just configuration. It is also used to build systems such as servers that are again configurations or physical assembly tasks. Common tasks are upgrades or adding new subset of a system through configuration.
        Defect: Standard Issue Type & Sub-task - The default way to create defects is as sub-tasks connected to a story. This block the story from deployment as it can never be closed with open sub-tasks. The standard issue type is used when defects are found without direct connection to a development or when you want to break out a defect as a known defect, but still close the story for deploy. Defect can only happen before code is put into production. I usually rename the standard Bug issue type to Defect if possible, otherwise I create a new issue type for it.
        Incident: Standard Issue Type - Incident is used for defects that are found after the code is put into production. It is separate from defect in order to properly identify where a defect has been discovered as that can affect legal aspects. It is also used to allow proper focus and prioritization as production defects usually need high attention. All incidents are standard issue types as the stories they comes from have already been closed.
        Feature Toggle: Sub-Task (optional) - This is a bit of an odd addition lately and it act as a way to determine what code is in what code based, even if it is not activated. We will not dig to much into this one as it's an article in itself. It is just added in case you work with feature toggle in your project. Test & Acceptance
      Test / Acceptance: Standard Issue Type & Sub-task (optional) - This is again an optional issue type due to the fact that most test add-ons have the functionality needed to keep track of time and effort. In the event that you need a way to add time and effort outside the add-on, then you can create an issue type for this as placeholder for that information. Generic
      Epic: Epic - This is standard in Jira and it is used, as described above, to group standard issue types.
        Task: Standard Issue Type & Sub-task - Tasks and Sub-tasks are standard in Jira and they can be used for any task not defined in other issue types. This can be things like scheduling meetings, organize workshop or buy cake for the team.  
      Color coding for visual guidance
      In order to make it even easier to identify what the different issue types will be used for I always create custom icons and color code them. This visualize the area of responsibility as well as the purpose of the issue types. My way to color code is based on color theories and my own preferences, so feel free to adjust if needed.
      Requirements - This is an interpretation of the business need to Development. I tend to color Business in blue/teal as corporate colors and Development as red. The combination of those two is purple, so I make the Issue types related to Requirements as purple.
        Development - This is the heart of the work flow. We tend to want incidents and defects highly visible as well, so we pick the color that match those requirements. We tie this into the traffic sign colors used in test and acceptance as well. This is why everything related to development is red.
        Test - This is where code is either allowed to pass to acceptance, or pushed back to development for further adjustment. It is something we want to make sure it has good attention and we also follow the traffic sign color schemes used in development and acceptance. this is why test is yellow, sometimes with a orange tint to tie it closer to development.
        Acceptance - This is where a need is given the thumbs up or the big GO. We use the traffic sign color scheme to signal this and for that reason Acceptance is green. I use icons that I feel is matching the issue type itself to further clarify purpose. I also use en inverted design to distinguish between standard issue types and sub-tasks. You can see some of the icons in the download section. You are free to use the icons in your Jira instance as they are created by me using the free version of fontawesome.
      Setting up Issue Types in Jira
      Now that we have defined the issue types and designed the icons it's time to set this up in Jira. I will set this up in my Demo Jira which is cloud based. If you use Server or Data Center version the way you set this up will look a little different, but the functionality will be the same.
      In order to get the new issue types into our project we will need to do three things:
      Create the new Issue Types Create a new Issue Type Schema and add the Issue Types to that Schema Assign the Issue Type Schema to our project.  
      Create Issue Types
      In Jira Cloud we do this under Jira Settings -> Issues -> Issue Types. Please note that you need admin access for this step. Here you will see a list of the current Issue Types and in the top right corner you will have a button that say "Add issue type". Clicking on that will give you a popup where you can create a new issue type.

      Once you add the name and description of the new issue type, then you select what type of issue type you want it to be. You can not add an image at the time I am writing this, so you will get a generic icon for it when you click add. Once created you simply find it in the list and click edit to change the icon by uploading a new one.
      Next to the icon click "Select Image" and then "upload avatar" in the popup. Select a new image, close the poup and then click on update to save the new image.

      Create a new Issue Type Schema
      Under Jira Settings -> Issues -> Issue Type Schemes you find a list of the different issue type schemes you currently have in your Jira. In the top right corner you find a button with the text "Add Issue Type Scheme". Click that to create a new scheme. Please note that you need admin access for this step.
      When you create the scheme you add a name for the scheme, a description and then you drag the issue types you want to add to the scheme from the list on the right to the list on the left. Once you have done that you can select "Story" as the default issue type. This will make Story the pre-selected issue type when we click on Create in a project using this Scheme. Once done, click save.

      Add Issue Type Scheme to your project
      Go to your project and then click on project setting in the left menu. It should be at the bottom of the list of areas for your project, but if you can not see it then you may not have admin rights for your project and you need to get some help with this step. If you have access then in the project settings go to Issue Types.
      This view will show you the current issue type scheme and the issues included in that scheme. In the top right corner you will see a drop list with a cog wheel that say "Actions". Clicking this will allow you to edit the issues in the scheme, but we want the other function called "Use a different scheme".

      Simply select the Issue Type Scheme created earlier by first making sure you select "Choose an existing issue type scheme" and then the correct issue type scheme in the list below. Click OK and your project will now be associated with the new issue type scheme we created and with that we now have our new issue types.

      We now have the proper issue types we need to work, but in order for them to really useful we need to make sure we have workflows that match the work we do. This is what we will focus on in our next article: Setup Jira & Confluence for success - Part 3: Defining Jira Issue workflows.
  • Who's Online   0 Members, 0 Anonymous, 3 Guests (See full list)

    There are no registered users currently online

  • Create New...