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


    69 stories in this category

      1
      Votes

      Atlassian, CVE-2022-26134, and You

      thejiraguy.com - I am still playing catch-up. When I was sick with COVID, I was down and not up to writing or reading a lot. Don’t get me wrong – I was fortunately vaccinated, which helped me recover very quickly, but it still felt like a really bad flu. 
      So, when my inbox and news feed started blowing up the day after I got my positive COVID test result, I wasn’t too interested in digging into it. However, the IT world waits for no one, and not even four days after the CVE was announced, I got an interesting email from my VPS Host.  
      0
      Votes

      JSM: Linking Insight Custom Fields

      community.atlassian.com - Hi Community,
      In this tutorial we will show you how you can dynamically change the options of an insight object field depending on a previous insight object field selection.
      We'll be creating insight object custom fields that are linked to each other and display them in the portal. When a Business Unit field is selected in the portal, we will only display the associated programs.
       

       
      Key Syntax used:

      Issue Scope (IQL)
      ObjecType = "Object Name" Filter Issue Scope (IQL)
      Insight_Object_Attribute_name =  ${customfield_ID}   
      Thanks,
      Fabian
       
      0
      Votes

      This chart predicts when projects will be done!

      community.atlassian.com - Hello Jira Community,
      If you’ve ever been managing a project of any kind, you know how important it is to have a good idea of when you can expect the work to be done. Today we’ll learn about a chart that does exactly that!
      I’m Vova from the Screenful team. We build productivity analytics for modern leaders. Our Jira integration makes it easy to create dashboards and reports from your issue data and share the actionable insights with your team. Today I want to show you how we forecast our team’s workload and how you can do it too.

      Screenful’s newest Workload (forecast) chart may look similar to the Workload (planned) chart which I talked about in April. While the Workload (planned) chart was based on the set start and end dates for the issue, the new chart makes forecasts based on your historical velocity. Instead of set start and end dates, it looks at how fast you've completed work in the past and makes predictions assuming your future delivery speed will correlate with your past performance.
      Getting started with forecasts
      Getting started is easy and can be usually done in under two minutes: simply create a Screenful account, connect your Jira projects, and navigate to the new Forecasts section in the Insights tab:

      The topmost chart shows your historical velocity as the amount of work completed per week. Below is the new Workload (forecast) chart that shows how long it takes to complete the remaining work based on the velocity history shown above.
      These two charts help you to see your past velocity, and get a data-driven forecast for the remaining work. Instead of guesswork, you can use the data to make your own judgment!
      Chart customization
      In addition to creating Workload (forecast) in the Insights tab, you can also create it as a custom chart to then attach to your dashboards or scheduled reports. For this, go to the Charts tab and click Add new chart → Blank new chart, and select the Workload (forecast) as the chart type. The chart editor opens with the chart settings. You can select one or more data sources and any of your numeric fields as the unit. Here’s an example chart:

      How to read this chart?
      The chart shows a burndown of the remaining work on a weekly total until all the work is done. The leftmost bar is the current week and the rightmost bar shows the week when all the work is completed. As the work progresses, the remaining work reduces until it goes to zero.
      At the top of the chart, you can switch between the Most likely, Optimistic, and Pessimistic scenarios. The most likely scenario assumes that you will complete the same amount of work (e.g. issues or story points) as you’ve had on a median week in the past. In the Optimistic scenario, you will complete at least the same amount as the top 20% of the weeks in the past. In the pessimistic scenario, you will complete as much as the bottom 20% of weeks in the past. The percentiles are configurable in the chart settings so you can specify to yourself what you consider most likely, optimistic, or pessimistic for your future delivery speed 😃
      In the above example, there are 173 open issues right now, and it will take 10 weeks to complete the current backlog of work to be done.
      By default, this chart assumes that you will complete roughly the same amount of issues per week as you have done in the past. It uses a 12 weeks median as the basis for the forecast but you can adjust it in the settings.
      And that’s how easy it is to tell when a project will be done!

      That’s it for today. As always, I’d love to hear from you. Please do not hesitate to comment on this post or reach out to us at hello@screenful.com if you have questions or feedback.
      0
      Votes

      Discovering content just got easier with related pages!

      community.atlassian.com - Hello Community, 
      Tim from the Confluence Cloud Product Management team here.
      I’m excited to introduce related pages, a new feature that uses smarts to help surface relevant Confluence pages.
      Have you ever gotten to the end of a Confluence page and thought “well, now what?” We’ve got you covered! Related pages are automatically generated suggestions for further reading, based on pages that are viewed or are organized together. This helps you gain context on collaborative work faster, and quickly discover relevant articles in a knowledge base, even when the pages aren't linked or organized together.

      This feature is on by default. Here are a few things to keep in mind:
      Admins can choose to turn this off at the space level under Space settings > Related pages.
      Permissions are respected, so only pages you have access to will be shown.
      If related pages are on for a space, page contributors can also show or hide on a case-by-case basis. If you choose to hide, select More actions (•••), then Advanced details > and either Show related pages or Hide related pages.
      This is only available on pages at the moment, not blogs.
      This is only available in Confluence and is not currently available in Jira Service Management customer portals. Related pages is currently rolling out, so it should come to your site soon if you don’t see it on your Confluence Cloud instance today.
       
      Questions, feedback, or comments? Let us know in the thread!
      0
      Votes

      How Use of Jira Dashboards Improved our Marketing Team's Efficiency

      community.atlassian.com - Yesterday I had an interesting dinner conversation dedicated to Marketing in 2022. Many marketers I know have already switched careers or struggle to find the joy of working in marketing anymore (and think about changing their jobs).
      I'm not an exception, though. I'm slightly bored after too many years dedicated to different marketing aspects. To keep the fire burning, I consistently try to:
      Learn and experiment more.
      Use my experience to support others.
      Take care of teams' efficiency.
       
      If you are deeply involved in the Atlassian Ecosystem, you already know marketing here is not messing around. It requires more than a basic skillset to fit your marketing approach. You must be intelligent, creative, simple, and efficient to stay noticed.
      After my short Atlassian retirement, I came back as a member of a brand new marketing team full of ideas and looking forward to a bright new future. As exciting as it was, I also had this dark thought in my mind: “I’m so sick of marketing.”
      Thankfully, we had much to work on polishing our brand, partners, apps, teamwork, and collaboration. When there is a struggle, my heart is happy. 💙
      For a couple of months, we expanded our team, created a new workflow, and began the broad adoption of Jira and Confluence as our primary sources of collaboration and planning. And immediately stumbled on the question:
       
       
      You may have a team full of high-performing individuals, but each person's definition of “productivity" varies tremendously. So we needed precise data to prove we were on the right track.
      As Atlassian users, we have the great advantage of using apps and integrations to automate and excel our processes even further. As app builders, sometimes we use them for free! 😃
       
      Grumpy Pro Tip: if you are an Atlassian marketer and are not using your apps. It's No Good.  
      I've already explained our fancy new process, but let's dive deeply into how Jira Dashboards help us do our jobs better.
      (If you are new to Jira Dashboards, here are 5 Atlassian tips for creating a killer agile dashboard in Jira Software)
       
      Our General Marketing Dashboard

      We track our marketing department's long-term and short-term progress on our primary Jira Dashboard. Long-term is our progress since day 1 of tracking, and short-term is our current Sprint.
      We keep it simple and self-explanatory. You need to glance over the board to see if everything looks good. With New vs Done being our most important metric, we closely examine the graph's movement. As you can see, so far, so good 🙂
      While the lines are synchronized in their moving up, I'm sleeping well.
       
       
      Content Dashboard

      Especially for our mighty content creator, the Content Dashboard is there to list only two metrics: ongoing work & simple progress chart.
      Why it's valuable to us?
      Never hear "So… what are you writing now?" again.
       
       
      Events and Partners Dashboard

      We recently onboarded a new team member responsible for our events, partner relationships, and internal activities (Welcome to the team, Jane! 🎉 )
      While moving through her Jira & Confluence onboarding, she was slightly confused by the number of metrics we wanted to track on only one board. Jane immediately shared her need for a separate Scrum board and Jira Dashboard to track her activities more precisely.
      Remember my number 3 fire-starter?
      If Jane is searching for a way to become more efficient, we have a common goal!
       Her Dashboard consist of:
      partner to events tasks ratio;
      progress charts for each activity;
      New vs Done for the past month;
      latest updates and work in progress.
       
      To me, it feels good to have a visual representation of our progress. It improves our mood, shows if any issues are present, and saves time from people "researching" what our activity state is.
      It keeps the CEOs happy as well. 😉
       
      0
      Votes

      Permission Schemes in Jira - Simplified

      reddit.com - Permission Schemes in u/Jira can be confusing. If you've ever felt overwhelmed or confused on how to configure the right permissions for your Jira project, you have to check out my latest #tutorial https://youtu.be/FEUsPMs-ymU
      submitted by /u/apetechda
      [link][comments]
      0
      Votes

      Confluence Cloud Bug Fixes - June 2022 🐞

      community.atlassian.com - Hi Confluence Community, 
      My name is Kuldeep Kaushik, and I’m an Engineering Manager on Confluence Cloud. The Confluence engineering team is continuously working behind the scenes to fix bugs, in addition to delivering new features shared on the community.

      Here's a summary of the high impact bugs fixed over the last couple months.
      Summary of bug fix  Fixed by Affected customers Watchers of bug ticket  Adding multibyte characters (like Japanese characters) in page title were causing same text to be copied in page body content
        21  25 Jira Issue Macro was not displaying the correct value of epic field   25 31 Users on instances with 3rd party themes installed were not able to access Space settings or create a page from global create option   20 21 Jira Issue Macros and Gadgets with complex filters failed to display the result   16 22 Content API endpoint’s metadata expansion was returning incorrect value   16 12 Updated large content id support for apps by providing content id as string (via Webhook)
        14 12 You can find the whole list of bugs we fixed recently here. We hope our bug fixes are making your life a little easier on Confluence! 
      0
      Votes

      Are you experiencing sprint review fatigue? Use Confluence to shake things up

      community.atlassian.com - As per the Agile gods, your teams and stakeholders get together every sprint for a review. The idea is to have immediate feedback. Helping us all steer the boat in the best direction. Another goal of the sprint review is mutual accountability. Scrum team measures their progress, and stakeholders are recommitting to their sponsorship.
      Alas, in real life, often time sprint reviews are floundering. Instead of a useful ceremony, they become wasteful box-ticking exercises. They see dwindling participation, boring presentations, and an apathetic audience. A large number of stakeholders, competing priorities, too much juggling, remote working, and zoom over saturation. These are only some of the factors working against good sprint reviews.
      Is this your organization? Are you the project manager that needs to drag people into the sprint reviews in the slim hope of getting even a single new insight?
      Why not try a different approach?
      This is how one organization transformed its sprint review process.
      The key ideas were simple:
      Share data with everyone: developers and business leaders alike. Spare everyone the face to face presentation. Recognizing that not everyone needs to hear everything, they made all the information available on Confluence. Everyone had access to the data and could dig into it, skim through it, or skip it altogether. Their choice. Elicit a-synchronous feedback, through Confluence. The project manager committed to following up on each comment raised in Confluence. Replace the face-to-face review meeting with a face-to-face AMA(ask me anything) session. Anyone could raise any questions for discussions and debate. Confluence was chosen as the central tool for this new system. As the organizations intranet it was the natural choice. From the CEO to the technical writer, developers and marketers, everyone were very comfortable using Confluence.
      As the wanted to get everyone engaged, using a platform everyone liked gave them a head start.
      How to organize a Confluence area for effective sharing of sprint data?

      The PMO had a dedicated space for sharing information about the project. The project manager added the sprint reviews as a sub-tree in this space.
      The list of information for each review was pretty long. They wanted to make it easy for people to locate the bits that interested them, so they split the data into several pages. The structure was consistent across all sprints. Each sprint review will have a collection of pages like this:
      The main page. It included: Sprint goals Key challenges The list of other pages related to this review. This was the list of child pages. The Confluence macro “Children Display” generates this list, so there is no need to manually update it . The PM configured the macro to show the excerpt of each of the child pages. Like this the main page was more informative. People liked that it helped them judge if they want to spend time on the child page. A page for performance charts. Like the burndown chart. The scrum master downloads these reports and puts them in Confluence at the end of each sprint. A page for the Jira issues in the sprint. Most of our stakeholders have no access to Jira so the PM used the Jira Snapshots for Confluence app to create this page. With Jira Snapshots, we also have a static copy of the Jira data, which helps keep the scrum team accountable. See more about this in the next session. (Disclosure: I am with the vendor of the Jira Snapshots app) A page with the bugs solved in this sprint. This page uses a Jira snapshots report for the same reasons described for point 3. Each demo is captured in a video, on its own page. Having each demo on a separate page makes it easier to find the demo that is of interest to you. The page excerpt for the video pages provides the scope of the demo. It also includes a shout-out to specific people, whose feedback we seek. Last page contains the recording of the sprint AMA session. Like this, people who can’t make the AMA could stay in synch.


      Another advantage of this standardization is that its easy to collect the data for each sprint.
      This is the easy process we go through to make the data available for each sprint:
      Step 1: during the sprint grooming, copy the “sprint review tree template” page, along with all its descendants, to create the pages for the new sprint. All the page titles are ready with a # in their title. Upon copy, Confluence replaces the # with the name of the new sprint. Step 2: When the sprint starts, the scrum master triggers the Jira snapshot in the Jira data pages. From that stage on, everyone knows what they planned for the sprint. Step 3: While the sprint is ongoing when a story is done, the developer may record a demo video. They immediately upload it to Confluence and move on. The scrum team loves this because it means less context switching at the end of the sprint. Step 4: at the end of the sprint: Scrum master copies the performance charts to Confluence. They also trigger a new snapshot to capture the Jira data at the end of the sprint. Step 5: Two days later: The team holds a sprint AMA session. They upload the recording to Confluence.  

      Use Jira snapshots to open up the Jira silo

      Before, in this organization, Jira was considered to be a silo. Most of the stakeholders did not have access to Jira, or did not know how to dig information from Jira.
      This was creating friction in the sprint review process. Developers and sponsors did not have the same information about the stories in the sprint. This led to everyone wasting time on questions and quarreling around this fundamental point. There was suspicion and mistrust.
      The Jira snapshot app solves this in a straightforward way. It copies Jira data into Confluence and displays it in a table there. The data is time-stamped, and static. Anyone with view permission to the page sees exactly the same data. Snapshots keep their history. Comparing sprint content between the start and the end of the sprint is a snap (sorry, could not resist the snap).
      Did you ever have an argument with someone about what was actually in scope or not in scope for the sprint? With Jira snapshots, this is a non-issue. Anyone can look at the snapshot from the start of the sprint and see.

       
      The new sprint review process turned out to be a pivotal change

      This new sprint review process propelled the organization to new places. Now, they were discussing real issues. Anything from. Topics like how to scope their sprints, what is a priority, and who their customer is, were analyzed, dissected, and improved.
      It's not that they no longer had challenges, but these were different challenges. Some people said that everything got less “political”. You can see this in even the smallest gestures. Developers are putting more heart into their demo videos, product managers are more thoughtful about how they provide feedback. The language of "us", and "them", no longer relates to the scrum team (us) and the people outside the team (them). Today, "us" relates to everyone in the organization.
      How are your sprint reviews going? Do you have your tips and tricks to share?
       
       
      0
      Votes

      Confluence Cloud has entered the (Microsoft Teams) chat

      community.atlassian.com - 👋 Hey Team, I’m Tygrr a Product Manager for the Confluence Cloud for Microsoft Teams app. 
      Last August, we launched a new Confluence for Microsoft Teams app, and I’m excited to announce that we’ve made it even better: Confluence pages can be viewed, edited, and created, directly within Teams — with the same macros and functionality you know and love.
      Without leaving Teams, you can now:
      ✅ Create a new Confluence page that looks just like the native experience
      ✅ Add rich formatting and macros to an embedded Confluence page
      ✅ Edit embedded Confluence pages in real-time with teammates
      ✅ Create and respond to in-line comments
      Teams and Confluence users now have a new hub for team collaboration and knowledge management.
      👀 See it in action with these interactive demos
      Adding Confluence Cloud to Microsoft Teams is easy!
       
      Edit your Confluence pages without leaving the chat
       
      Add existing Confluence pages to a Tab
       
      Create a new Confluence page
      The best part? The Confluence for Teams app is free and can be used with any edition of Confluence cloud (including the free versions).
      Learn more about MS Team and Confluence.
      Looking for more ways to integrate your Atlassian tools with Teams? Check out the full list of integrations here.
      0
      Votes

      Announcing Jira Product Discovery open beta - sign up today!

      community.atlassian.com - 👋  G’day Product Managers!
      We have been hard at work building a new tool for product managers, and today we’re proud to announce the open beta availability of Jira Product Discovery! This milestone is two years in the making, and we couldn’t be more excited to share our work with the Atlassian Community!
      Put simply, Jira Product Discovery helps product managers capture the why behind the work. You can set product priorities as a team, bring customer needs into focus, and seamlessly move from product ideation to customer delivery - all in Jira.
      Being a product manager is hard
      Let’s face it, product managers don’t have an easy job:
      It feels like you are constantly reacting to feature requests coming from the rest of the organization, rather than proactively offering up and testing new product ideas.
      There is constant pressure to keep leadership, other departments, and customers informed of product plans
      And all the while, you are drowning in tools. Flicking from one tool to another, you lose context and time and this stops you from delivering the best work of your life.
      With Jira Product Discovery, we’re making it easier for product managers to focus on the important discovery phase of product development – and doing so in an environment you already know and love.
      Ready to dive in?
      Get started here for free. If you’d like to learn more about Jira Product Discovery before signing up, check out the Jira Product Discovery website.
      Also be sure to join the Jira Product Discovery Community. This is the first port of call for our product team every morning with coffee. We can help answer your questions, you can interact with other early adopters, and you will also have a major impact on what the product ultimately becomes!
      We look forward to having you join the Jira Product Discovery beta! If you have any questions, please post them below. 👇
      Quick Links
      Learn more about Jira Product Discovery
      Sign up for the beta
      Join our Community
×
×
  • Create New...