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

    Atlassian Cloud changes Mar 16 to Mar 23, 2020

    • Like 1

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

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

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

    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.

    Next-gen: Epic panel in backlog rolling out icon.png

    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.

    New issue view: Add web links

    Save time and add context to your issues by adding web links in the new issue view. Web links are links to any URL, but they appear prominently below the issue description where they’re easy for you and other issue viewers to find. Use them to link to important sites that teammates might need to better understand an issue.

    We’re also moving all issue link types, including web links, into the Link issue button. Click Link issue to quickly link related issues or click the down arrow on the button to add links to web pages and Confluence pages (if you have a linked Confluence site).

    Find issues you've recently worked on rolling out icon.png

    We’ve added a new Worked on tab to the Your work page. This tab lets you quickly find and resume work on issues you’ve updated recently. Head to Your work > Worked on to get started.

    Improved navigation in Jira Cloud rolling out icon.png

    We’ve created an improved navigation experience that always appears at the top of the screen, with clearly labeled buttons and menus to help you search, create, and resume your work. Find out more about our improved navigation experience and when you can try it out.

    New issue view: Improved date formatting in the history feed rolling out icon.png

    Dates in the history are now more consistent. They’ll correctly show when changes happened relative to your time zone and be translated into the language you’ve chosen for Jira.

    Prevent cross-project commenting when replying to an email thread

    This release ensures that the comments added to a ticket, sent to the specific project email address, will only appear on the ticket in that project.

    Previous behavior

    1. Bruce receives an email notification about ticket - ABC-123 from his next-gen project “Facilities”
    2. Bruce comments in the body of the email, “This contract needs input from legal” and forwards the email to the next-gen project “Legal”.

    Bruce’s comments would be added to the ABC-123 ticket in the “Facilities” project.

    New behavior

    Bruce’s email will create a new ticket in the “Legal” project.

    Select your email notifications for issue activity from personal settings rolling out icon.png

    Jira sends email notifications when certain activities occur on issues. In your personal settings, you can now choose whether you want these notifications. If you do, you can toggle notifications for issue activity when you’re a watcher, reporter, assignee on an issue, when someone mentions you, and when you make changes to an issue. Learn more about choosing email notifications.

    Issue collector no longer matches the submitter's user session to make them the reporter rolling out icon.png

    We’ve adapted our issue collectors to the Chrome browser’s new cookie security features, but have had to change how they work. The issue collector no longer matches a submitter’s user session to make them the reporter. You can still match them by email address.

    To improve issue security, project and issue keys are no longer displayed in the success message after submitting feedback on an issue collector (unless the project is open to anyone on the web).

    Learn more about using the issue collector.

     

    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.

    Next-gen: More epic colors on the roadmap rolling out icon.png new this week¨.png

    There are now 8 additional colors for your epics on the roadmap. Simply click on an epic to see its details, and select the epic color to view the new options available. Learn more about managing epics on the roadmap.

    GitHub app on the Atlassian Marketplace rolling out icon.png

    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: Create child issues on your roadmap rolling out icon.png

    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.

    Kanban boards just got faster rolling out icon.png

    Is your team so productive, their 'Done' column is always overflowing? Too many issues on a board can slow it down and make you scroll way too much. To fix this, we’re bringing what we’ve codenamed “Fast Kanban”—a way to keep your board fresh and clean, and as quick as a flash.

    The idea behind it is simple. The ‘Done’ column will now show only issues that have been updated (in any way) in the last 2 weeks, hiding the rest. Less noise on your board means happier teams. Any project admin can change the retention period, or choose to display all issues, if they prefer. Learn more

    Quickly copy a link to an issue in your next-gen project backlog rolling out icon.png

    When viewing your backlog, you can now copy a link to an issue to your clipboard. To try it out:

    1. Navigate to your next-gen project backlog.
    2. Locate the issue you want a link for.
    3. Select More () > Copy issue link.

    The link to the issue is copied to your clipboard, ready for you to paste into a Confluence page, Slack message, or anywhere you might want to share your issue’s link.

     

    Jira Service Desk

    New issue view for Jira Service Desk rolling out icon.png

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

    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!

    Remind agents to update empty fields when moving a request in your next-gen service desk rolling out icon.png

    We added another rule to your next-gen service desk workflows. Now, you can prompt your agents to complete an empty field when they use a specific transition to change an issue’s status. The rule removes a burden on your teams to remember to fill in specific fields until they matter. It keeps them focused on the important work of helping your customers.

    To learn more about the rule, and get an example of how to use it, check out our complete documentation on next-gen workflow rules.

    Global create can select request type and raise on behalf of rolling out icon.png

    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 rolling out icon.png

    The new Confluence editor allows anyone to create beautiful, powerful pages effortlessly. Check out the editor roadmap to learn more.

    End of support for nested tables rolling out icon.png

    As we work on creating a more stable editing experience, we will no longer support nested tables - that is, a table within a list, block quotes, or another table. Existing nested tables will not be affected, you simply won't be able to create new nested tables.

    We're extending editing improvements to all pages on Android rolling out icon.png

    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.

    Jira issue URLs are converted to smart links rolling out icon.png

    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 rolling out icon.png

    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 rolling out icon.png

    Get to information faster with improved navigation – making what you need visible from anywhere in Confluence. Learn more

    Portfolio for Jira plan macro rolling out icon.png

    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.

     

    Bitbucket

    Pull requests now include a Jira issues panel new this week¨.png

    In the sidebar of the new pull request view, you can now see a list of Jira issues related to this pull request and Jira issues created in this pull request.

    New Code Review - Limit the amount of rendered diff content rolling out icon.png

    Limits the amount of pull request content rendered in the diff and file tree to improve browser performance. Limits include the overall number of files and number of lines for the entire diff. Learn more

    Show Jira issues assigned to the current user on dashboard

    You can now see your assigned Jira issues on your Bitbucket work dashboard.

    Recent repo cards on Bitbucket dashboard

    We’ve improved the way you see your recent repositories by adding a new section on your Bitbucket work dashboard.


    • Like 1


    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.

    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
      Atlassian promoted their Free version of Jira Cloud recently as their way to help remote teams during the Corona crisis. Like many I thought this was great and I moved over from the normal trial version I had. Today all my projects was gone and I just realized that the free version is severely reduced in function. It is in my opinion nothing more than a money grab to lure people in and make them upgrade to the $10 version.
      To trick people to sign up for a service without telling them that you are limiting the experience is a shady thing to do. To remove something as important as permissions for no apparent reason other than forcing people into buying another license is just greedy. The $10 version has always been something of a gift from Atlassian where they donated the money they made to charity. It feel so bad that now that they add a free version, which actually does not impact Atlassian's profit in any way, they water it down and remove features.
      That is just bad.

       
      I don't really care if Atlassian offer a limited version, but make sure you clearly market it as such. On the free site they do not mention this at all. I may have missed this when I made the change, but I did not see this when making the change from the standard $10 I was using and I sure as hell did not get any warning that the custom permissions I have configured would not be usable in the free version.
      I think it's unworthy for a company like Atlassian to abandon their previous practice of providing a $10 version that allow people to try out their products before they commit to a larger license model. To go out and promote the free version as some form of gift to help people to collaborate in an open and transparent way and they reduce the product by removing permissions is just not what I would expect from Atlassian.
      I can see no other reason than that this is a shady way to introduce people to Jira and then force them to upgrade to a "full version". That is such a long way from the caring and giving Atlassian of old...
      So if you have a license with custom permissions, if you want to manage permissions or if you like me educate people and need public access, then do not use the watered down and limited free version. If you are looking for a free tool to manage your tasks I am afraid I will not recommend Jira anymore...
      I am very disappointed.
    • By ©Jimi Wikman
      Requirements & Test Management for Jira
      MARKETPLACE.ATLASSIAN.COM Bring the whole software project right inside your Jira Decided to take this for a test run.
      Has anyone used it, or is currently using it?
    • By ©Jimi Wikman
      For many, many years visual designers have been working outside the workflow of IT. The way of working differ a lot from the more controlled IT deliveries, which has meant that design often comes as design drops rather than as a part of an Agile workflow. Today we have many tools that can change that, but how do you do that and what is the benefit?
      For many years visual design have been a messy affair with naming convention and external cloud storage where versions get put into a named folder structure. Sure it has been improved with tools that allow collaboration such as Figma and Invision. Handover to development have also improved with tools like Zeplin and Avocode. Still, the handover process, when it even exist, is far from streamlined and it causes quite a bit of a mess.
      Even with collaboration tools and development handover there is still no control over changes to the visual designs. Versioning, automatic or even manual is not the same as version control after all. Why is it important to be able to control versions? The reason is that in a continuous delivery situation design changes  need to be controlled and agreed upon before they are turned into code. This is especially important if you do not work in a design system or at least in an Atomic Design pattern.
      In order to fit into a continuous delivery way of working, which is where I think most companies are moving towards, we as designers need to fit into the way development work already. So how do we do that without compromising the exploratory nature of our craft? Let us first define what it is that we need to do in order to sync visual design work with development work:
      Collaboration - We need a way to quickly get feedback on visual designs so we can adapt and adjust. This comes from stakeholders and developers so it must fit both groups. Controlled deliveries - We need a way to deliver visual design in a controlled way that is not only easy to understand, but also matches the work of the developers. Handover - We need a way to handover visual design to development that is easy to work with for the developers. Most of these are done today mostly in meetings. That is wasteful and it require a lot of time management. It also require that there are meeting spaces suitable for this work. In some cases it require that everyone is in the same location or that specific technical setups are made for external communication.
      There has to be a better solution?
      Indeed there is and it's not really that much of a pain to begin with this workflow for visual deign either. We will take advantage of the tools you most likely are already using and we will tweak the workflow a bit and add a few things that you may not use just yet. This workflow is for Sketch, but you can probably find similar way of working if you work with Adobe, Figma or the Affinity suite to mention a few alternatives.
      Atomic Design

      The first step is to start thinking of your design the same way that the developers (hopefully) is. By organizing your visual design according to Atomic Design you will have a one to one connection to the code. This is extra useful if you are using a design system as then the design changes you make will be reflected correctly in both the visual design and the code.
      Nest your symbols following the basic structure of atomic design and you will make the developers happy as they can simply make the same changes you do on the atoms and molecules. You will also find it much easier to continuously work from the smallest entity up as it makes creating new design elements fast and easy
      Abstract

      Abstract is a great tool that allow you to work in branches, just like the development team is doing. This allow you to commit to designs for delivery, but without restricting you from exploring alternatives at the same time. This is done by having different branches where only the Master branch is actually the one that is put in production.
      The way Abstract work fit very nicely into the development workflow. This makes it much easier to collaborate on the same cadence and it ensures that only the visual design that has been agreed upon by everyone involved is being put into production.  This is done by using the approval process built into Abstract any time you want to push design to the master branch.
      The final part of abstract is the handover where the developers get an overview of the design elements that makes sense to them. Things like measurements, color codes and more are all easily accessible from Abstract. There are other tools specifically designed for this, like Zeplin and Avocode if the handover features in Abstract is not enough. For me Abstract hold all the information I need, but every team have different need.
       
      Invision DSM

      Invision DSM is a design management system and it is where the final design we push to master get placed as the one truth. Not only will this be a fully functional documentation space, but you can also work with the components directly in Sketch by drag and drop. This allow you to constantly work with the latest visual design.
      You can integrate Invision DSM with your code as well to automatically push code directly into the documentation using Storybook. If you do not have Storybook, then you can manually add code to each component in the documentation in Invision DSM. If you want to extent the developer handover you can connect Invision DSM to Invision Inspect as well.
      Invision DSM is also part of a greater package so you get access to tools like Prototype to make your designs come to life and Freehand that is a collaboration space that is kind of like a mix of sketch and a whiteboard. You also get Boards that allow you to create mood boards with ease.
       
      Jira Cloud

      Most developers work in Jira today and most are on Jira Cloud, or on their way there.  You can connect Invision DSM to Jira directly using the Invision addon for Prototypes or by simply link directly to a section in Invision DSM. Jira will act as your task management so you can connect your design tasks directly to other tasks, such as development and test for example.
      If you are working within a SAFe organization, then design can be part of other types of work items such as SAFe epics or Features for POC work. If you are working in a smaller organization then you can get Jira Cloud for free, which is always nice.
       
      Why would you want to do this?
      What benefit would you as a designer get from changing your workflow in this way?  There are of course many benefits, but let us list the biggest reasons why making this change will have a positive effect on you and your design work.
      Reduce the barriers between you, stakeholders and development - By making it possible for everyone to stay on top of the design process as well as the development process in one place it becomes easier to break down the barriers that naturally are built in most cases. You reduce us and them situations and communication improve quite a bit. This allow you to become a part of the team because you work the same way as everyone else. Control the way your design turn into code - One of the worst things I know as a designer is when my design get turned into something horrible in development. This often happen when you as a designer is on the outside of the team and simply handover design. By working along side the developers and working with the same cadence as they do, it becomes much easier to maintain your design as you intended it. Using the atomic design and having a design system it becomes so much easier to make sure everything looks as intended in your design and changes can be done swiftly with minimum effort on all sides. Improve feedback to make better designs - By working in a controlled with alongside the development team and the stakeholder with tools that allow for rapid feedback and approval processes you get feedback faster. Often this feedback is also much better quality-wise as it is in the design itself and not a collection of emails or excel sheets. With fast feedback with great quality design work become faster and changes can be done almost instantly. Free up time by making information available to the developers - As a designer you spend a lot of time providing assets, color codes and information about the design. By automatically move this into a tool you can reduce that time a lot. This time can instead be spent on discussing designs with the developers to find great solutions together that are both visually appealing to the end consumer and technically easy to build and maintain. Keep everyone up to date with the design process - How may screens, videos, prototypes and power point presentations have you not made to keep different groups up to date on your design work? Having everyone in the same tools make that so much easier. The trick is just that the tools have to be useful for everyone as well, which is why so many design tools fail in that regard. Abstract and Invision DSM are different in that regard since it is useful for stakeholders and developers alike. If this is not enough to convince you, then as icing on the top you should know that the tools integrate with Slack as well. So you can get the best communication flow possible...
      So, what do you say, does this sound like a workflow that you would like to see expanded with more details? If so, what would you like to learn more about first?
    • By ©Jimi Wikman
      Join us from anywhere to see how to work better, together.
      It's no surprise that teamwork today looks very different — even from just one week ago. Whether your teams are together, or working from home, be a part of Atlassian Remote Summit and learn about how everyone can work better together from anywhere. Register today to stay current on all Remote Summit news, then tune in live when the event begins on April 1st. 
       
      *Registration for this online event is free of cost.
×
×
  • Create New...