JIRA provides a convenient lens for anticipating changes to an application. But correlating a new version of the application (i.e., a new build) with the FixVersion on its associated JIRA issues can be difficult because these two meanings of the word “version” are not tied together in any programatic or enforceable way. An issue marked with FixVersion “1.3″ may have been implemented in an application version called “1.3-RC1″, “1.3.0″ or even back in “1.2.9″.

In the last two years the Bamboo team has had a lot of conversations with customers big and small about their deployment problems and they have always circled back to one issue: visibility. That is to say, there is a lack of visibility across Development, QA and Ops teams about what code has been written, how it was tested, and whether specific changes have made it into production.

If you use home-grown scripts to deploy your software, or even one of the CI servers currently available, making upcoming changes highly visible is difficult. That’s why in Bamboo 5 we harnessing application versions to connect issues, their commits, and the test and deploy history of the resulting build.

Wait: JIRA already has version tracking

Why do we also need versions in Bamboo, you ask? Fair question. Well, version tracking in JIRA is all about tracking changes as you work towards a goal or milestone–it doesn’t actually represent the software version that your deploying. For example, it make take a few builds and deploys to QA until you’re satisfied that the software is ready to ship and you can mark the version as released in JIRA.

By contrast, Bamboo’s versioning provides a unique identifier for the build that’s being deployed: the version name you choose for it (“1.3-RC1″, for example), plus a roll-up of all the new commits and associated JIRA issues since the last version. This makes it dead simple to get a complete picture of what happened between any two versions.

Dude, where’s my code?

Versions in Bamboo are tracked against your environments. Environments are another new concept in Bamboo 5, used to represent a server or group of servers that you want to deploy to. Typically these are given names to that reflect the environments in your IT infrastructure like QA, Staging, and Production.

By looking at the environments for our deployment project, we can see what versions are currently running, giving a quick overview of what’s been deployed and where. Only a single version can be active on an environment at a time, and any previously-deployed versions can be looked up through the deployment project’s version history.

Through the eyes of JIRA

As useful as all this information is, you won’t need this level of detail all the time. Age-old questions like “Where can I verify this bug fix?” and “Has this user story gone out to production yet?” are what most of the team will be asking most often. So Bamboo 5 brings that information to where you already are: JIRA.

Inside each JIRA issue that is associated with a version of your application, you’ll see a list of your environments and whether the code for that issue has been deployed to each one. This also works with the new issue detail view on search results just released in JIRA 6.

Connecting JIRA issues with versions in Bamboo is simple: just include the issue key in the commit message when submitting code for the issue (something most developers do instinctively anyway). Bamboo will see that and add it to the list of issues worked on since the last version.

Versions are just one aspect of the continuous delivery goodness coming up in Bamboo 5. We’re pretty excited about it all, and we don’t mind saying so! We’ve even made pre-release builds of Bamboo 5 available for you to try out. Install it, kick the tires, and use the in-app feedback button to let us know how we can make it even better.

Get the Bamboo 5 beta

1. Meet JIRA’s new header

The new header makes it easier to navigate JIRA, and match the look and feel to your organization’s brand. The new header’s application navigator lets you link related applications to JIRA so they’re just a click away. Linking your frequently-used related applications to JIRA lets users quickly access other applications for higher productivity. The application navigator supports Atlassian products, as well as third-party applications.

In addition, the create issue button has been promoted to a more prominent status in the header, and we’ve tightened up the help and JIRA administration links to make them clearer to users.

2. Quickly apply your brand to JIRA

By default, the JIRA header uses the blue and white theme shared by all Atlassian applications. However, our fictional friends ActiveCorp would like their JIRA instance to match their logo as well as their red, green, and black brand colors a little more closely. In JIRA 6, they can upload their logo and brand colors in in the look and feel section of JIRA administration.

ActiveCorp used the new look and feel configurator available in JIRA and Confluence. With the upload of their logo JIRA’s header was instantly updated to match their brand.

Pretty neat, yeah?  For those of you that saw the JIRA Jr. promotion, we used this feature as well to make a kid-friendly version of JIRA.

Branding tools across your organization helps bring a consistent look and feel across your tools making it easier to for end users to navigate between applications. JIRA is now easier than ever to brand for your organization.

Want to experience the best JIRA yet?  Try JIRA 6 today.

Try JIRA 6

Modern. Fast. Mobile. Simple.

JIRA 6 is a completely new JIRA. The redesigned look and feel brings a whole new user experience to JIRA. It is modern and simple, clearing away the clutter so that you can get your work done faster. It’s also mobile so you can work with your project on the go. Check it out:

Play

 Enjoy the preview? Register for the What’s New in JIRA 6 webinar today.

Sign up for the JIRA 6 webinar

Modern

JIRA 6 introduces a modern experience that follows the new Atlassian Design Guidelines (ADG). This new user experience doesn’t just look great, it also helps you get your work done faster. Information is easier to find and common tasks are simpler. The new JIRA look and feel is consistent with other Atlassian applications, so users are more productive using JIRA alongside Confluence, Bitbucket, Stash, and other Atlassian products.

Fresh new look

We’ve made a big investment in the look and feel of JIRA. In addition to a more consistent experience across other applications using the ADG, like Confluence and Stash, we’ve modernized JIRA’s look. Updated buttons, icons, menus, and typography bring JIRA into the now. All of these changes make for a smoother experience inside of JIRA.

Navigate with ease

Your most frequently visited pages and recent activity are just a click away from anywhere in JIRA. The new common header gives your team an easy way to work with other applications, including Confluence, Stash or another JIRA instance. You can link any Atlassian or third-party application.

Fast

Detail View: optimize the way you work with issues

JIRA 6 brings about an awesome new way to work in JIRA. With detail view you can now easily see all your issues both at a glance and in detail on the same screen. We’re on a mission to make teams faster. With JIRA 6′s detail view, it’s much easier to work with sets of issues because you never lose focus. Detail view gives you the full power of JIRA: inline edits for single field changes, @mentions to pull others into the conversation, and keyboard shortcuts to speed up navigation and make editing and triaging issues a breeze. We think these new features will cut the time you’ll spend working with lists of issues by 50 percent.

Compact mode

Nothing aids productivity like screen real estate. Compact mode in JIRA 6 adds up to 20 percent more screen space to help you focus on what matters most: your issues. In list view, compact mode allows you to add more columns to the screen. In detail view, you can see even more issue specifics without scrolling.

Power User? Press ‘[‘ to collapse or expand the sidebar without touching your mouse.

Mobile

Access JIRA anywhere! We’ve introduced a new mobile view for JIRA, focused on the activities and information you need when you’re not gazing deeply into your monitor’s pixels.

We’ve optimized how teams work by enabling you to stay connected even when you’re out of the office. Comment on issues and @mention others to bring them into the conversation on your train ride home. If you’re stuck in a meeting, assign an issue that needs attention straight from your phone. Check out your favorite filters to see the updated status of your stories. Watch hot issues so you stay on top of any updates.

After all, where are you usually checking email and seeing JIRA notifications? Your phone! Just click any link in a JIRA notification from your smartphone, and you’ll wind up in the new JIRA mobile interface.

Simple

Get started easily

In JIRA 6 we’ve made getting started easier than ever. We’ve taken the types of projects you create most often in JIRA and collapsed the setup for those projects into two clicks. Creating new projects couldn’t be simpler!

Workflow

Thousands of teams choose JIRA for the awesome power of the workflow, but you don’t have to start from scratch. Discover, explore, and import workflows in the Atlassian Marketplace.

• Bring known best practices into your organization from the Atlassian Marketplace.
• Configure and test workflows (including screens and fields) in your staging instance. Import them to your production instance to minimize configuration churn.
• Find workflows for all kinds of business processes in the Marketplace. Explore new possibilities and find creative ways to take advantage of JIRA.

JIRA 6 has even more!

JIRA 6 is filled with all kinds of good stuff. You can check out the release notes for more details, but here’s a few more key feature of JIRA 6.

1. Editable usernames — The second most requested feature, as determined by customer votes, is here! JIRA Administrators can now edit any username in the JIRA internal directory.
2. Bulk watch — With over 220 votes, we’ve brought this feature into JIRA 6. Now you can watch issues en mass to stay in touch with key issues in your project.
3. Global workflow schemes — Now you can edit an active workflow scheme on a set of projects. If you have many projects that share one workflow, this feature is for you.
4. Translate custom fields — Running JIRA in multiple locales? Customers whose users operate in different languages can now translate the names and descriptions of custom fields.
5. JIRA to JIRA issue copy (Marketplace plugin) — For customers with more than one JIRA server, you can copy an issue from one project to another, even if the projects aren’t on the same JIRA instance.

Ready to explore the best JIRA ever?

JIRA 6 is not just a fresh coat of paint. We’ve made the core experiences at the heart of JIRA better. JIRA 6: Modern, Fast, Mobile, Simple. JIRA 6 makes both individuals and teams more effective in achieving their goals. It’s time to try JIRA 6 and see how it makes your team run faster, together.

Register for the What’s New in JIRA 6 webinar today.

Sign up for the JIRA 6 webinar

New to JIRA?

Get up and running in a matter of minutes with a free 30-day JIRA OnDemand trial.

Ready to upgrade?

Check out the full release notes and start seeing real results with JIRA 6 today.

OnDemand Customers: Congrats! You’ve have been auto-upgraded to JIRA 6!

Check back to http://blogs.atlassian.com/jira/ over the next few weeks. We will be highlighting key features and use cases using the new JIRA on the blog.

As individuals, we can get a great return on investment from optimizing within that inner loop. These are the tasks you and your team perform every day–even several times each day–so it’s critical that they be fast and effective. Most of these tasks are, or can be, tracked as issues. As agile organizations, we’re always seeking to work with issues more fluidly so we can bring our innovations to market faster and with higher quality. Let’s take a look at the product feedback life cycle:

Bugs and issues are expensive. Handoffs between people cost time and tools can go a long way to make collaboration a cost savings or a cost burden. Tooling can and does make a big difference. Let’s take a look at a company that has 30 engineers at $80 per hour:

The JIRA team is devoted to making teams more collaborative and more effective. With JIRA we’ve optimized how your team and your tools work together to so that your team can work unencumbered. Let’s take a look at a few experiences that make JIRA the platform of choice for today’s leading teams.

Detail view: make working with issues fast

Issue triage is one of the most expensive things software companies do on a recurring basis. It usually involves multiple senior engineers and managers reviewing lists of issues to ensure that the team is most effective in the next sprint. With JIRA 6, detail view makes bug triage faster with a single page experience where you can browse and edit issues. JIRA pre-fetches issue data so that you don’t have to wait for page reloads and refreshes. Detail view has trimmed the JIRA team’s triage sessions by 65 percent.

We’ve also enhanced list view with a new compact mode, so you can see more of your data on small screens and projectors. When working in triage sessions with others, pixels matter. With compact mode there is significantly less scrolling over prior versions of JIRA. If you’ve not customized the columns in list view to show more of your data, you are missing out on one of the best benefits of list view. Compact mode results in less scrolling, making you more efficient in triage meetings working in both list and detail view.

For Agile teams, GreenHopper’s new rapid boards make using Scrum or Kanban equally fast. Greenhopper uses the latest web technology to boost performance by pre-fetching data so you can quickly update your team’s agile board. You can effortlessly drag and drop issues to note progress. It’s faster than using sticky notes, and teams can follow your progress, whether they’re local or remote.

Integrating with other tools

JIRA is one of the core applications used to drive innovation in today’s software companies. Giving engineers a seamless experience between tools saves both time and money. JIRA integrates with Atlassian applications as well other products to make collaboration more effective.

JIRA and Confluence

Product and project managers need the latest data to inform and steer the organization. JIRA’s integration with Confluence make it easy for engineers to work in JIRA. As the engineering team makes updates to issues, those changes show up in Confluence so those outside of the engineering teams don’t have to constantly ask for status updates.

JIRA and development tools

JIRA seamlessly integrates with Stash and Bitbucket to bring a best-in-class Git workflow to your teams. Users can reference JIRA tickets in Git commits. Stash or Bitbucket automatically update JIRA with the relevant commit information. Bamboo then builds your product and places build history right inside the ticket.

JIRA also integrates with Fisheye and Crucible to bring the same features to organizations that use centralized version control systems like Subversion and Perforce.

Integrations abound!

The Atlassian Marketplace contains hundreds of add-ons that extend the power of JIRA. Updating to the current version of JIRA helps ensure you’re using the latest technology to unlock the power of new add-ons.

Ready to write some custom integrations for JIRA? JIRA now includes a stable REST API, which is much more powerful than in prior versions. The big leap forward in the REST API is that you can now work with sets of issues using only one API call; the API is fixed for an entire major release. With JIRA 6, we won’t introduce any breaking changes until JIRA 7. You can build your applications with confidence and know well in advance when any important changes come.

If you have an app that should be notified when an issue in JIRA changes, then webhooks are for you. JIRA can notify other applications programatically when important changes happen, like creating, resolving, or reopening an issue. For example, JIRA can connect with an SMS service to notify users when an issue gets resolved.

Speed at scale

JIRA isn’t just faster for the individual. Atlassian understands the needs of larger teams: no matter how big you plan to grow, Atlassian is right there with you. We know that teams grow in many different ways, so we’re providing you with more information on how to scale large JIRA instances effectively in your organization.

We’re committed to helping you work faster. In JIRA 5.1, we poured a ton of work into JIRA’s internals for performance and scale. The efforts of Atlassian’s two new performance-focused development teams have given JIRA big results so far, most noticeably a 40 percent increase in throughput when comparing JIRA 5.1 over JIRA 4.4. JIRA scales better, too: JIRA 5.1 performs at the same level with two and a half times as many issues as JIRA 4.4! In JIRA 6, we focused on optimizing your interactions with JIRA. JIRA 6 brings the detail view as well as new UX to make you faster than ever with JIRA.

Growth shouldn’t slow your teams down. As your team scales, searching for the right set of issues to focus the team becomes critically important. JIRA’s new search interface fully integrates search into the issue navigator. The outdated left handed column search is no more! JIRA’s search interface follows you. As you select search criterion, JIRA updates the search results in the background so you can quickly see if you are getting the right search results.

Once your search is dialed in, it’s easy to make updates in JIRA. You can take action on search results right in the issue navigator’s list view.

Staying connected has its privileges

Why should you renew? When you renew your relationship with Atlassian you bring the best-in-class tools to your teams. We’ve made a lot of improvements to JIRA in the past year that all center around one theme: to make your teams more productive. Engineers love great tools; make your team happier and more productive by giving them JIRA 6.

Not to mention, a current support contract gives you full access to Atlassian Support. Atlassian’s support engineers are available 24/7 to troubleshoot problems and answer questions on configuration.

Ready to take the next step?

Renewing is easy. Just email sales@atlassian.com to get started! If you’d like to learn more about what makes the next version of JIRA completely awesome, check out what’s new in JIRA 6.

Try JIRA 6

Growth makes things complicated!

Growth is a good thing; it enables ideas to foster and come to market. Growth also makes things tough because culture and processes don’t always scale along with the size of your business. Scaling isn’t just about big companies; scaling doesn’t mean enterprise. At its core, scaling is about investing in that culture and those processes so they don’t fall apart. It’s about making sure your ideas and your team can continue to grow unencumbered. Let’s define a few terms:

• Gain: The benefit the entire organization gets from its tools and process
• Friction: The frustration, angst, and hassle factor an organization feels from its tools and processes
• Net Gain: Gain minus friction

Any process involves friction, but the key is maximizing net gain. When you recognize and minimize friction from the beginning, you can scale smarter.

An idea starts with one

Great ideas often start with with just one person. As the idea begins to unfold you’re faced with your first set of tasks, and the inevitable question: how does one manage that list of work? When you’re a team of one, it’s easy to create a simple list of issues to drive your workflow; you just use a small task list application, or a list of things to get done in an Excel spreadsheet. You add new things to the list, and cross things off as you get them done. Simple, right?

Annoyances start with two

Then another person joins the fun, and you become a collaborative organization! The process that works for one person generally scales well for two people: you can sync your task list manually via a meeting, or though a shared Excel spreadsheet. And even though it works fine, it’s more time consuming than working alone. In other words, there’s more friction.  But you get more done with two people, so you deal with it.

More people, more friction

As you start adding more people to the project, that’s when the real headaches start. With each new person it gets harder to manage the project, because small task management systems simply don’t scale. Let’s look at some of the common problems that plague growing organizations.

Excel never learned to share

Hosting an Excel spreadsheet on a shared file server isn’t the most collaborative option. Make no mistake: Excel is a great tool, and we use it every day at Atlassian. It’s just not a great team task management solution. With one master copy of the project plan on a server, concurrent editing by multiple people isn’t an option. The entire team is blocked on every edit, or a project manager has to manually collect each and every detail. Both options waste everyone’s time.

With email there is no clear source of truth

Solutions that involve sending task lists via email are a mess: duplicate versions of the task list live all over the place, the original gets diluted every time the list is copied, and the work plan becomes more and more out of sync. Things that should be simple–like a task reassignment–result in two people will having different versions of the plan, and potentially working on the same thing. Duplicating efforts is never a good thing.

Tracking history is a pain

Effective project managers look at historical data to help them drive future results.  To do this right, one needs a tool that gives insight into past performance of the team to make effective estimates. Tools with limited historical tracking features make it tough to get the right data needed to plan for the future.

So how can JIRA help me?

One shared source of truth

JIRA reduces friction as there is one master copy of your project but everyone can contribute to it.   You can use flexible workflows to structure each project’s work items; JIRA flexes to the way your team wants to work. And since it’s designed to be shared, everyone can update their items and track the overall status of the project. Let’s take a look at what puts JIRA above other task management solutions.

Issues have clear assignees so ownership across the team is clear. Need to change who is working on a task? When reassigning an issue, JIRA automatically notifies the new recipient that they have a task waiting.   JIRA integrates with your company’s directory server so it’s easy to get started.

No team works exactly the same way. JIRA’s configurable workflow engine captures just the right structure for your team.

Project managers have access to detailed history to more effectively plan future work

Track everything in one place. The days of hunting through email to find the latest status update are over. JIRA’s flexible dashboards make up-to-the-minute status reports a breeze.

JIRA makes growth easy

JIRA is just $10 to get started with up to 10 users. Think of it this way: “For just 10 bucks, my team can have best-in-class project management tools.”  As a bonus, you can feel good about your purchase, because Atlassian donates all the proceeds from our 10 user licenses to Room to Read, a nonprofit helping to fight illiteracy around the globe.

Today’s leading teams use an Agile workflow like Scrum or Kanban. JIRA makes migrating to agile easy as well; just add GreenHopper to your JIRA install, and you’ll unlock all the power of agile and still have best-in-class issue tracking.

Starting right makes growing easy. You can add users to your license incrementally as you grow. JIRA is available on a hosted platform for a turnkey solution, or running on your hardware for maximum flexibility in deployment.

Get started today

JIRA 6 makes both individuals and teams more effective in achieving their goals. Learn more about how JIRA is used by many different organizations on our customer case study pages. Want to learn more about the power of JIRA? Check out the JIRA project tour.

Try JIRA 6 and see how it makes your team run faster, together. Get up and running in a matter of minutes with a free 30 day JIRA OnDemand trial.

See what’s new in JIRA 6

I’ve got great news for you: JIRA 6.0 is coming soon!  Amongst many great new features, this release of JIRA will support bulk watching of issues.

Atlassian has a public JIRA instance, jira.atlassian.com, where we get a massive amount of feedback from our customers.  When making decision about how to evolve a product like JIRA, the product managers consider a wide variety of factors: customer content, community forums, support, Atlassian Experts, in-product feedback, as well as votes and issues from jira.atlassian.com.  We heard y’all loud and clear on JRA-2429: Bulk Watch.  That single issue has 229 votes!

So, how will you be able to bulk watch issues in JIRA 6?

First, Subscribe

Subscriptions and bulk watch go hand in hand to keep you connected to JIRA.  Subscriptions keep you abreast of a large set of issues, while bulk watch keeps you informed about all the small updates.  Let’s walk through a simple example to see how these features work hand in hand.

• Subscriptions let you stay on top of a large set of related issues. You can subscribe to any filter in JIRA, and you’ll be emailed a consolidated version of those issues.
• Bulk watch lets you subscribe to individual notifications for each issue at once.

You are a development manager with a program nearing release.  You want to be notified when someone files a blocker or critical issue.  You can create a filter in JIRA that matches those criteria.

Let’s set up a simple filter in the Issue Navigator.  In JIRA, click Issues->Search for Issues from the menu bar.

In this example we are looking for all open issues for the JIRA project that are blocking or critical for version 6.0. We then save this search as a filter. If we click details, we can then subscribe to that filter.

Whenever a new issue matches that filter, JIRA will email you.  You can set notifications to whatever period you want. For example, you can make sure the list of critical issues are in your inbox every morning.  As new issues come in, you can decide if you want to watch them to follow all the issue traffic.

Now, Bulk Watch

Watching an issue notifies you of any changes to that issue.  In JIRA 5.0.3 we enabled autowatch by default.  This feature adds anyone who comments on an issue as a watcher.   As a development manager nearing release I want to get detailed notifications on some key issues in my program.  In prior versions of JIRA you’d have to find each issue individually and watch it.  Now you can do so in bulk. Using our filter above, we can use the bulk change feature to watch a set of issues.

The first step in the bulk change wizard is to choose the issues from the filter results you want to change.  It’s OK if your search is a bit broad.  As the development manager I may only want to watch most, but not all of the issues that match my search.  In the bulk change wizard it’s easy to opt out of some of the issues.  When you press next, the highly voted option appears!

With two more clicks you will become a watcher on all the issues selected in the prior step.  Pretty cool, aye?

WARNING: While bulk watching issues is useful, it can also generate a lot of email traffic.  Once you no longer need to watch an issue, you can bulk stop watching issues to ensure that JIRA is only sending detailed emails on the issues you care about.

This is only one of the great new features in JIRA 6. Be the first to find out when JIRA 6 is released.   Sign up for the JIRA Insiders Email!

Subscribe

The one thing we heard loud and clear is that you’re looking for a way to share all the tips and tricks out there with the rest of your colleagues. Enter the JIRA Tutorials YouTube playlist!

This playlist is where we keep our best up-to-date tutorials showing off keyboard shortcuts, tips about searches and filters, and killer admin tips like editing the set of workflows in your project. And if you’re keen to get tips and tricks straight in your inbox, sign up for the JIRA Insiders email list!

Sign up for JIRA Insiders

The Tip of the Month, brought to you by Atlassian University, is a monthly series to help master Atlassian tools. Products are more fun to use when you know all the tricks.

One of the great things about our customers is that we see great diversity and individuality across our customer base. That’s you, our reader! Some customers build software with JIRA, others design clothing, educate students, and some even make cars! One of the great things about JIRA is that it can be customized to really reflect your organization. Custom fields are a great way store additional data in JIRA. For example for an issue type of bug your team may need a field called platform (Mac, PC, Mobile) to know the environment where the issue reproduces. If you track customer leads in JIRA you may need to add in a custom field for company. Once all that data is in JIRA, it’s helpful to see it in a table so it’s easy to see at large.

Want to scan issues faster?

The Issue Navigator is one of the core views in JIRA. It’s the view that shows a set of issues from a search result. For most software projects JIRA’s defaults work pretty well. Many different types of teams use JIRA to track very different types of processes. Have you ever wanted to change what shows up by default? You can add that new field into the search results to see that data in context.

Why Customize the Issue Navigator?

Customizing the issue navigator allows you to see the right data at the right time. This month’s tip focuses on getting the most out of the list view in the issue navigator. Let’s say we need to review a set of bugs for the next sprint to prioritize what the team fixes. Knowing what version a bug surfaced in can help guide when that bug should be fixed. To customize what shows up by default, just click Tools -> Configure Columns when in list view.

Changes in the column configurator don’t affect JIRA’s search results. It only changes what fields JIRA returns with each search results. Let’s add the affects version field to our search results. To add that field, just choose affects version field in the add new column dropdown.

Once we add it, we can see a preview of the new data in the table below. Using the JIRA team’s project as the example we can see:

What’s truly great here is that you now see this data inline with the other issue attributes. You can sort this column to group all the issues with the same version together. This way it becomes easy to see all the open issue that came in by version. Having that data makes prioritizing issues much easier.

JIRA uses the last search to populate the data below so you can see example data below. Changes using the above method will only show up for the current user. We don’t recommend removing the issue key column. The issue key is the only guaranteed unique identifier on an issue. It’s of special importance to JIRA. It’s the only way to ensure you are referring to one issue in the context of work or conversation. Also, the summary column is the visual cue to what the issue is. We recommend you keep that one as well in all views.

You can change the order of columns by using the arrows underneath the column header. To remove a column just click the trash can icon. Also, keep a watchful eye on the number of columns on the screen. Ideally you will have enough screen real estate to ensure that the browser does not need to scroll horizontally. If you need to view a large number of columns in a one time scenario, we recommend to use the export to Microsoft Excel. To do so, click Export->Excel (all fields).

A Note for Admins

Want to make the change globally? As a JIRA admin, you can set defaults for all users by going to JIRA Administration -> System -> User interface -> Navigator Columns.

Have the latest JIRA?

If you do not see list view in your JIRA 6 or OnDemand instance you may be in a new view in the issue navigator called detail view. To follow along choose the list view option from the Issue Navigator.

As a side note, we encourage you to try detail view. It’s one of the great new features of JIRA 6!

Did you discover a setting you didn’t know about? Post a comment below.

If you found this helpful, please visit Atlassian University – interactive tutorials and videos with tons of tips just like this one.

One of the highlights of our tour was teaming up with London Girl Geek Dinners to host a night of tech talk, beer, wine and munchies. Held at London’s Google Campus, the event followed on from our San Francisco Girl Geek event in November. The theme of the evening was remote working, inspired by Yahoo’s recent decision to revoke the right of staff to work from home full-time.

Watch highlights of the evening:

Atlassian’s own Director of Corporate Communications Catherine Norman and Judith Lewis of London Girl Geek Dinners hosted the evening. Astrid Byro, remote worker extraordinaire, was the guest of honor and main speaker. Managing IT projects and teams from the mountains of the Himalayas using JIRA on a Kindle Fire, Astrid was the perfect speaker for our controversial subject of teleworking.

Flexibility is the new black

Attendees took a great interest in Astrid’s tales of working from horse trails and cliff edges, and bombarded her with questions about connectivity, software, batteries, data files and management skills. Astrid’s talk was followed by a lively debate on remote working with members of the audience who expressed their views and experiences of the practice in the tech industry. Not surprisingly, most women felt that too many firms have old fashioned, outdated approaches to the concept of remote working, and that more flexibility should be given to workers. The audience agreed that most issues with flexible work arrangements can be overcome with a little trust and communication.

For more extreme instances of remote working (such as Astrid’s scaling the Himalayas), Astrid offered the following tips and tricks:

• Find the right power/weight of equipment ratio.
• Check out power bars – many people aren’t aware of them and they are massively useful for remote working (and daily life).
• Use li-on batteries carefully and alternate them with spares.
• Use a device with a built-in cellular connection rather than tethering a mobile or using MiFi – the latter two burn batteries and may not work across different devices.
• Avoid unforeseen complications by testing your gear on outings before you need it for work.

We also made sure that no geek left empty-handed, dishing out a plentiful supply of our rockin’ Girl Geek t-shirts to all in attendance.

Thank you, London. We hope to see you on our next trip. And if you can’t make it, just connect remotely. Even if you are halfway up a mountain, you no longer have an excuse!

Kudos the Confluence team for the inspiration for this video