Plan better with JIRA Portfolio 1.9

We're excited to bring you JIRA Portfolio 1.9, which makes planning even more realistic. The new capacity visualization makes it easy to see how much work can get done and provides transparency if targeted deadlines are not realistic. Flexible sprint configuration makes sure your portfolio plan reflects the way your team actually works, so you can accurately plan. And now you can update your teams' work day settings so JIRA Portfolio doesn't think they're working over the weekend and on Christmas.

Continue reading »

If you rely on email for internal support, chances are valuable time is wasted going back and forth trying to get the right information. Work is assigned inefficiently, leading to slower resolution times and unhappy customers. Plus, you're not able to report on progress to show the value of IT to the rest of the business.

Continue reading »

We often collect feedback and requests from people outside of our team. If they find a bug, need something done, or have a feature request – somehow and some way, they need to reach us. As an Atlassian, I prefer working in JIRA. It’s my favorite place to plan, track, and get things done, however, I find that sending colleagues (who are often non-technical) to JIRA introduces them to an unfamiliar interface they don’t necessarily know how to navigate.

Continue reading »

When I joined Atlassian, I had heard of JIRA and Confluence, but had never used them. During my first day at the office, I was joined by other new hires and taken through our onboarding. We covered important items like which systems were tied to various passwords, the passcode for the alarm, and, most important, how to order lunch. All of these tidbits of information were helpful, but taking it all in was like drinking from a fire hydrant. That's when they introduced us all to the "extranet," or

Continue reading »

In the coming weeks we’re updating the site with better global navigation, cleaned-up information architecture, standardized page layouts, enhanced screenshots, and improvements to key content. We’re also making some important structural changes, particularly a decision to shut down page comments. The decision comes at no small cost to Atlassian’s technical writing team. All of us appreciate the chance to speak directly with customers and fielding questions and digging into specific use cases is a great way to learn the ropes of a product. So why did we make the call?

Continue reading »