Jira apps for agile teams

Product development without an agile workflow would be like building a house without a blueprint or defined roles on the construction team. No one knows what to do or who does what. 🤔

The result: time and energy wasted building a single house that would most likely reveal its darkest flaws over the years.

So, here’s what you need to know: Process increases efficiency. It also increases efficacy, customer satisfaction, and a better experience for the team members who take a part in the process.

Follow this how-to guide to building and implementing an agile workflow in Jira. In this article, we’ll cover what an agile workflow is and define the steps for its creation and its principles in depth.

The notion of workflow

The execution of a team's work is dictated by one or more processes. In other words, a process is a way the team gets to the finish line with deliverables. And if you're developing products with an agile framework, an agile workflow is a way to structure that process.

Generally, a workflow is made out of:

• Activities, tasks, and steps
• Roles
• Work products
• A few other things to help improve team collaboration and work execution

With such a structure, it gets easier:

• To repeat the process
• For team members to work with each other
• To scale the process and the work itself

Breaking down tasks and milestones is the secret sauce that keeps agile projects running smoothly. Think of it as slicing a pizza: small, manageable pieces are far easier to handle and much more satisfying in the end.

Start by taking your big project goals and chunking them into bite-sized tasks. Each task should be small enough that the team knows exactly what needs to be done, but not so tiny that tracking them turns into busywork.

Next, set clear milestones that act as checkpoints along the way. Milestones aren’t just calendar dates—they’re meaningful accomplishments your team can rally around. This could be anything from getting a prototype out the door, to finalizing a core feature.

Here are some tips to help:

• Prioritize clarity: Make sure every task and milestone is easy to understand and leaves little room for ambiguity.
• Balance ambition with reality: Yes, everyone wants to move fast. But setting milestones that are just out of reach only leads to frustration. Aim for steady, sustainable progress.
• Keep dependencies visible: If Task B can’t start until Task A is finished, call it out. Tools like Trello or Asana make it easy to map these relationships.
• Minimize handoffs: Try to group tasks in ways that reduce waiting around for someone else to finish their part. This keeps things flowing and spirits high.
• Plan for improvement: If a milestone reveals a hiccup, be ready to revisit your task breakdown. Agile is about adapting—not sticking rigidly to the first plan.

Breaking tasks and milestones down this way helps your team stay organized, focus on delivering value, and adapt quickly if the winds shift—as they almost always do in any well-intentioned workflow.

Key phases of a typical project management workflow

Let’s break it down: while every team tweaks their approach, most project management workflows travel across four core stages—each playing a vital role in getting things over the finish line.

• Initiation: This is where the foundation gets laid. Teams hammer out the “what” and “why”—clarifying project goals, scoping out requirements, and rallying the first set of resources. Imagine drafting blueprints before even thinking about construction.
• Planning: Once the vision is in focus, it’s time to make things actionable. Here, teams split the work into tasks, divvy up responsibilities, schedule key milestones, and line up the resources needed. Think of this as laying out the job site so each crew knows what’s next.
• Execution: Now the work kicks off in earnest. Teams tackle tasks, stay aligned, and adjust on the fly as obstacles pop up. The plan meets real life, and the collaboration (with a good dose of coffee) begins.
• Monitoring and control: Nobody wants to end up with a lopsided house. This phase is all about tracking progress, reviewing what’s been done, and fine-tuning the plan as needed to hit targets—ensuring nothing important slips through the cracks.

Breaking the workflow into these phases helps teams stay organized and nimble, no matter what the project throws their way.

It seems like a workflow is so well-organized that teamwork would flow smoothly just because it exists. Well, that's not the case. In the next section, you'll learn that there's not a workflow for any team or project. Instead, there are one or more workflows that work for your team or your project.

Why there's no one-size-fits-all workflow

The size and maturity of teams have an impact on their workflows. Also, the type of project and both company culture and team culture influence the configuration of workflows. Bottom line: Your agile workflow will depend on many factors, and it’ll likely be unique.

You might, however, find online suggestions of workflows that prove to work with other companies. So, if you prefer, you might use those as a starting point for the definition of your own workflow. It might be the case that excluding some steps does the trick for you. On the other hand, you might define your own workflow from scratch.

Jira is a very versatile solution for workflow management that supports many different agile workflows.

With Jira, you may customize workflows to different company cultures or team cultures. In this context, culture means the way team members work with each other. In the same vein, a workflow expresses the dynamics of a team in one or more projects.

Now, if we're talking about Jira workflows, you should know what one of those contains.

What's a Jira workflow exactly?

A Jira workflow is an agile workflow built on top of and implemented with the help of Jira. It's a digital board that allows checking the statuses of work items. It may also send notifications when those items change status. You can also use your Jira board for Scrum meetings such as daily standups and sprint retrospectives.

You absolutely need to keep the statuses of ALL work items accurate. That means updating the status of each work item whenever and as soon as it changes.

Only an up-to-date agile workflow — and Jira board — fulfills its purpose and delivers benefit. It's an awesome tool for team members, Product Owners, and Scrum Masters to track work progress at all times.

How epics, user stories, versions, and sprints shape agile ways of working

So, what’s the secret sauce behind those smooth-running agile teams you keep hearing about? It’s all about breaking down work into manageable, meaningful pieces - enter the power squad: epics, user stories, versions, and sprints.

• Epics are the big-picture building blocks - the “what’s our destination?” moments. They capture large, complex features or goals, offering a zoomed-out lens for mapping progress over time. Think of an epic as your team’s long road trip.
• User stories are the smaller, more focused tasks that ladder up to those big goals. They translate what users want (“As a music lover, I want to save favorite playlists…”) into clear chunks for the team to tackle. Imagine them as the pit stops along your journey - each important, each achievable.
• Versions, sometimes called releases, offer natural breakpoints for delivering value. They help you organize and ship finished work to customers in batches, much like dropping off care packages at scheduled intervals.
• Sprints are the timeboxed working sessions, typically one to four weeks, where the team concentrates on a prioritized set of user stories. By the end of each sprint, there’s something tangible to show for the effort, keeping momentum and morale high.

In combination, these agile elements keep teams organized, focused, and flexible. They allow you to break daunting work into digestible steps while still adapting quickly to change. And when you’re using Jira, this framework ensures that everyone’s rowing in the same direction (with fewer bumps along the way).

Let's move on to our guide now. You'll find out, one tip at a time, how to become an agile workflow rockstar with the help of Jira.

Your guide for agile workflow in Jira

Start your engines! You're heading on a fabulous learning journey about the creation and management of agile workflows in Jira. Here are our best tips to make this process happen:

1. Start now

Don't postpone getting your hands dirty with workflow definition.

Even if you start simple, just get started. Don't delude yourself into thinking that you'll succeed at agile if you start big. In fact, that could work against you and your project.

2. Don't overwork

Don't spend weeks structuring, restructuring, and then restructuring your workflow some more.

Overworked workflows are hard to understand and much harder to implement and comply with. That would harm the basic principles of agile methodology.

With an overloaded workflow, you'd end with team members not knowing what to do and when to do it. Consequently, at the end of the sprint — or iteration — and project, no deliverables would be ready to roll out.

3. Don't forget about workflow stakeholders

You should account for roles that will somehow use the workflow you're defining. Whereas some will use it daily to get work done, others will use it only for some kind of management analysis.

You should understand with them what their workflow needs are. It'll take time, so you must be patient.

4. Understand the concept of ‘issue’ in Jira

In project management, an issue describes a problem for which there's no solution yet. Those issues come from risks to the project's development process and ultimate success. For instance, adding a functionality to the project scope — the issue — could come from the possibility of requirement changes — the risk.

However, in Jira, an issue doesn't necessarily represent a problem. Rather, it represents a piece of work that teams must complete. For instance, a Jira issue can be a task or a helpdesk ticket.

With software development, a Jira issue may symbolize more specific concepts such as:

• Product features and functionality that the development team must implement
• Bugs that must be solved

5. Know the pieces of the puzzle

In Jira, a workflow has four types of components:

1. Status. This indicates the position of an issue in the workflow. It can be an open — or unresolved — status or a closed — or resolved — status.
2. Transition. This defines how an issue changes status, and it can be either uni or bidirectional. You can create more or fewer constraints depending on how statuses change. You can even define that only certain people or certain roles can change an issue from one specific status to another.
3. Assignee. This is the person responsible for an issue.
4. Resolution. This describes why an issue went from open to closed statuses. Additionally, it should only stick to an issue while it’s resolved.

In software teams or projects, it's common to find statuses such as:

• "To Do" for issues yet to start
• "In Progress" for issues that the team already started to tackle
• "Code Review" for completed coding tasks that need a review
• "Quality Assurance" for completed issues that require testing by a team of testers
• "Done" for completed, reviewed, and tested work

When a code review is successful, the work is done. In this example, the code review's success is a transition from the status "Code Review" to the status "Done." And the resolution would be the reason why the code review failed.

Finally, you can set up transitions with:

• Conditions. They prevent an inadequate role from changing the status of an issue.
• Validators. These ensure a transition only occurs under certain circumstances. If not, the transition doesn't happen.
• Post functions. They describe actions on issues besides changing their status, and you can automate them. For instance, remove the resolution from a resolved issue before changing its status back to unresolved. Another example would be to remove the assignee from that issue.
• Properties. These are characteristics of transitions. For example, one characteristic could be to only show resolutions relevant to the type of issue.

6. Define ‘done’

Every team is unique. It’s made up of different people, different habits, and different experiences with technology and methods. Different ways of getting work done. This means you need to define what “work done” means to your team or your project.

For instance, you need to answer the following questions for your team or project:

• What status should a product or a feature have when it’s approved to launch or release?
• What should your team members do to get each work product to that status?
• Who should make decisions — such as approvals — along the way, which decisions, and at which points?
• Who declares work as done?

7. Customize Jira default workflow

Remember that you could use Jira to customize workflows to different ways of working as a team? Here’s how to do it:

Step #1: Define your workflow's statuses and transitions in Jira workflow designer.

You may go with Jira default Scrum or Kanban workflow — Jira classic templates — or make some changes to it. Alternatively, you may choose the Jira simplified Scrum workflow, which is adequate for reasonably basic requirements.

The simplified version of the Scrum workflow contains:

• Three statuses: "To Do", "In Progress", and "Done"
• Two transitions: from "To Do" to "In Progress" and from "In Progress" to "Done"
• Four columns to organize issues distributed across boards: "Backlog," "Selected for Development," "In Progress," and "Done"

Step #2: Build your workflow by adding components to the simplified Scrum workflow.

To track issue progress in agile development, you might add statuses such as "Code Review" and "Quality Assurance." And, you might add a validator to the transition from "Code Review" to "Done" to force that you need a successful code review to mark “Done.”

In addition, you might include approval stages in the workflow such as "Awaiting QA." These stages are prior to those in which an issue is closed or changes to a closed status.

Step #3: Nail the visual presentation of the diagram.

Once you finish tailoring the workflow to your team or project, make sure that the diagram is visually readable. That's essential when sharing the diagram with stakeholders for feedback. You should collect feedback from at least one representative of each kind of stakeholder.

An interesting feature of Jira is the workflow lets you give visual highlight of issues. This lets you see where the issue is in the workflow according to its status. Just open the issue and click on the "View Workflow" button next to the issue's status.

8. Rely on Jira reports for progress tracking

Jira provides two useful reports for tracking the team's work progress on a sprint:

• The Burndown Chart, which shows:
• The amount of work left to do in a sprint
• The work that team members are executing at the moment
• The distribution of work throughout the sprint
• Whether issues fit into the sprint and the effort estimation was adequate
  
• The Sprint Report, which includes:
• The Burndown Chart
• A list of open and closed issues for that sprint
• Extra work added to the sprint

As with any other report, Jira reports allow you to reason about success and failure. In this case, it's the success and failure of each sprint in terms of:

• Effort estimation
• Team performance
• Process irregularities
• Sprint planning

Most importantly, you can use Jira reports for the continuous improvement of those aspects and preventing problems such as:

• Too much work for a sprint
• Rushing work
• Sudden changes in priorities

A Jira workflow comes in handy when detecting outliers in the development process such as:

• A large number of open issues
• Frequent issue reopening
• A high number of unplanned issues added to the sprint

Being able to detect these problems is extremely valuable in that it helps avoid a massive sprint failure.

9. Share information

People at your company who aren't members of your team might need information from your workflow. So, take that into consideration when defining your team or project's workflow.

Those people might need to know about:

• The amount of completed work
• The product backlog dimension when compared to team performance
• The number of open and closed issues or the number of issues in a specific status
• The average issue completion time
• The average number of issues that take too long or experience bottlenecks, which means not moving forward at specific statuses such as "Quality Assurance"

10. Keep it simple

⚠️It can be tempting to create issue statuses while moving issues through the workflow, but don't do it! Each additional status adds more transitions and all their customized characteristics.

❌If your workflow already allows you to assess the sprint and feed your stakeholders with valuable information, that's just perfect. You don't need to add more issue statuses to it.

✔️Add extra issue statuses only when you have no other option. For instance, when different teams need to track work in different stages of development, you might need different statuses.

11. Limit work in progress

You may determine a specific limit to the number of issues in a specific status. When doing so, you should make sure all the team has enough work at each workflow status.

Plus, you should ensure that the limits you introduce into the workflow don't exceed the team's capacity. If you don't, the team will need to prioritize and you may not want that to happen.

Team performance should increase if you set the right work-in-progress limits. 🤗

12. Prepare to scale up

Agile teams should be small. Nevertheless, an agile workflow should cope with an increase in the number of people working with it. This means no one should notice if an increase takes place.

Here are some golden rules for scaling agile workflows:

• Agree on agile practices for workflow definition and minimize customization when multiple teams working on their own projects must collaborate.
• Different teams working on the same project should use the same workflow, or things could get messy.
• Teams should compromise when defining a common workflow. However, that's when teams build workflows based on multiple past successful experiences.

What else can you do?

Whenever you hear about workflows, it’s a sign that the work’s execution is being structured. It's also a sign of a long way ahead, but the outcome will be awesome if you:

• Follow the 12 rules above
• Choose a flexible issue tracker in terms of workflow customization, such as Jira
• Complement the issue tracker with the right apps

Don't force your team or project to comply with a tool. 😨 Rather, do the exact opposite! Choose the tool that allows you to build and implement the right workflow for your context.

That will increase throughput and workflow compliance levels, which is exactly what you want when creating a workflow.

Keep your agile approach strong — streamline, discuss, and iterate. These are the keywords for building and implementing an agile workflow, so don't forget them for a single second! As a result, you'll avoid:

• Complicating the workflow when it's not absolutely necessary
• Disregarding the pains of stakeholders and team members have when using or viewing the workflow
• Having an outdated workflow that's no longer adequate for both the company culture and the team culture

Kick your agile workflow up a notch

Easy Agile TeamRhythm helps you build and implement a Scrum workflow in Jira. Optimize your agile workflow by:

• Visualizing what the team will deliver and when by arranging user stories into sprint swimlanes
• Prioritizing user stories in each sprint by ordering them inside the respective sprint swimlane
• Reviewing sprint statistics at a glance to ensure that the team's capacity isn't exceeded
• Registering effort estimation in user stories.

You can stick to manual Scrum workflow, or you can automate with free Jira software. We know which method we prefer.

Whichever you choose, implementing the Scrum framework creates a streamlined workflow. Each person has a specific role throughout the framework's steps.

The Scrum workflow provides team members with a simple process to help teams meet stakeholder needs.

While agile methodology aligns with Scrum, Kanban, and Lean, here, we’ll focus on what a Scrum workflow is and how this methodology can support organizational teamwork.

What is Scrum?

Teams use the Scrum framework to guide their workflow. Having a structure to follow means they can easily share, track and improve their deliverables.

Scrum divides work into smaller work parcels known as sprints, which typically last 2-4 weeks. Once the sprint is over, team members do a sprint retrospective meeting (also known as a sprint review) to chat about what worked well and what can be improved.

Before jumping into sprints and stand-ups, it’s essential to assemble your Scrum team. Scrum is all about collaboration, so you’ll want to make sure you have the three key roles filled: Product Owner, Scrum Master, and a well-rounded Development Team. Each member should understand their responsibilities from the get-go, promoting smooth communication and effective teamwork throughout the project.

Scrum roles

Let’s look at the different roles that make up a Scrum team.

1. Product owner

The product owner has a core role in the Scrum workflow. They guide agile team discussions about product backlog items and features. In addition, product owners guide quality assurance to make sure deliverables are up to par.

More than a backlog manager, the PO is the team’s link to customer value. Their job is to say no just as often as yes, prioritize ruthlessly, and make sure the team is solving real problems—not just checking off requests.

2. Scrum Master

The Scrum Master will closely follow the principles in the agile manifesto to support sprint planning. Scrum masters guide development teams through agile methods to add value for stakeholders.

Part coach, part process watchdog, part shield. The best Scrum Masters don't just “remove blockers”—they teach teams how to see and solve problems themselves. They’re protectors of healthy process, not project managers in disguise.

3. Software development team

Development teams are skillful and cross-functional. Teams that work in agile software development environments will typically include designers, developers, testers, and others to prevent the need for external assistance.

This group owns the work together. Scrum works best when the team is cross-functional and collaborative—not when individuals stay in narrow lanes. Everyone should feel responsible for the sprint goal.

With the basics in place, we can take a closer look at the agile workflow stages.

Components of the Scrum workflow

The Jira workflow involves an iterative feedback cycle that focuses on creating value throughout the product development process. You can use the basic Scrum workflow steps or customize these.

The parts of an agile workflow are as follows.

1. Backlog development

A product roadmap guides team members in creating user stories and product requirements, which make up the sprint backlog. In the backlog, teams propose a list of features or user stories that the team must deliver. Product owners decide which features will make up the backlog.

2. Backlog release planning

Produce owner and team collaboration now decide which user stories will make it into each backlog release. Each backlog release is the completion of a smaller set of activities which eventually make up a sprint release. After completing this planning and setting timeframes for each action item, team members choose specific features for each sprint.

3. Sprint planning

Sprint planning kicks off the sprint, when team members complete a set of backlog tasks within predetermined timeframes (usually 14-28 days). The team defines a sprint goal and selects which backlog items to tackle. They estimate the time and complexity involved and break work down into tasks.

Example: Your team selects 6 user stories focused on mobile onboarding. During the 2-week sprint, developers and QA collaborate in parallel, with mid-sprint demos to gather feedback early.

4. Daily Stand-ups

Agile teams use these daily standup meetings to track their agile workflow towards meeting sprint goals. Daily standup meetings are typically held — naturally — standing up, as they should last no more than 15 minutes. Standup meetings help teams discuss solutions to daily work issues.

5. The burndown chart

Team members can use Jira software to create their burndown charts. Burndown charts show original time estimates compared to real-time activities, which shows where expectations or team resources need to be adjusted.

6. Testing and validation

During testing, the team demonstrates product functionalities for stakeholders. Feedback from product testing guides any needed changes.

7. Sprint retrospective and follow-up planning

The final phase of the Jira workflow is to hold a sprint retrospective. Sprint retrospectives are post-mortems on the previous workflow. At this stage, agile teams question what they did well, what didn't go as they hoped, and what changes they should make in the next sprint. Groups hold these sprint retrospectives to concentrate on better value deliverables through continuous improvement.

Jira software offers a visual display of the team's velocity, task progress, and project status. All these elements link back to the user story, and the group begins a new lifecycle to complete their project.

Track What Matters: Metrics to Guide Your Workflow

Metrics help Scrum teams improve—but only if they’re used to learn, not judge.

• Velocity: Tracks work completed per sprint; helpful for forecasting.
• Cycle Time: Measures how long it takes work to move from start to finish.
• WIP (Work in Progress): Monitors the amount of active work to prevent overload.

Use metrics to spark conversation: What’s working? What’s slowing us down? What can we try differently?

Common Pitfalls in Scrum Workflows (and How to Avoid Them)

Even with a clear workflow, things can go sideways. Here are a few common issues teams face—and how to address them:

• Overcommitting: It’s easy to assume you can “just fit it in” when planning a sprint. But overstuffed backlogs lead to missed commitments and team burnout. Be conservative, measure actual velocity, and protect focus.
• Retrospective Fatigue: Retrospectives often fade into routine—or worse, get skipped. The fix: keep them short, rotate facilitators, and use prompts that dig into team dynamics and process pain, not just “what went well.”
• Undefined 'Done': Without a shared definition of “done,” teams ship half-finished work. Agree on this as early as possible—including quality, tests, documentation, and review.

Create your Jira Scrum workflow in a few simple steps

You can either carry on using a manual Scrum process or transition to an automated Jira workflow for Scrum.

To create an automated, custom workflow, go to the Jira workflow designer. From there, you can manage the workflow scheme for your Jira project. You can also organize backlogs, complex workflows, workflow statuses, or view an issue status using custom fields.

In your workflow, you can:

• Use statuses like "In progress" or "Under review."
• View status items on lines for transitions.
• See issue resolutions.
• Check conditions that restrict assignee roles in bumping up issues to the following stage.
• Use validators to limit who can make transitions.
• Link further changes with transitions.
• Use triggers for automating transitions within specific parameters.
• Set workflow properties for transitions.
• Establish a link between the simple or complex workflow and issue types using workflow schemes.

As the agile team goes through the product lifecycle in a series of sprints, they need a tool to guide their journey.

With the free Easy Agile Scrum Workflow for Jira plugin, you can move Jira issues between the "To do," "In progress," and "Done" sections. You can also use the top right button to drag and drop specific issue types in the "Backlog" and "Selected for development" areas on the board.

More features from the Jira workflow plugin

In terms of automation, plenty of tools are available. You can use Easy Agile’s free Jira workflow plugin as valuable support for agile project management. This can help you create complex workflows and save all the details in the Jira cloud, ensuring nothing is ever lost. The free Jira workflow plugin also includes your burndown chart and sprint report.

Add the Confluence wiki tool to your Jira software for greater team collaboration. Also, use the Team Calendars add-on for better team collaboration.

Automate your Jira workflow now

Don’t wait for providence to come knocking on your door. Automate your Scrum workflow today with software that works.

We design agile apps for Jira with simple, collaborative, and flexible functionality. From team agility with Easy Agile TeamRhythm, to scaled agility with Easy Agile Programs, our apps can help your agile teams work better together, and deliver for your customers.

Efficiency is key for engineers, mastering keyboard shortcuts in Visual Studio Code can save valuable time and allow more time focusing on problem solving. Instead of navigating through menus, the right shortcuts let you code faster, refactor seamlessly, and stay focused. In this guide, we’ll cover essential shortcuts in a TypeScript setting that will streamline your workflow and boost your productivity.

IntelliSense Code Completions

Most the time you'll probably use code completions whilst typing but sometimes it can be quicker to manually trigger it to quickly get a property or parameter value. On both MacOS and Windows the shortcut is Ctrl+Space.

Code Snippets

This isn't necessarily a shortcut but I wanted to included it because it can save a lot of time when entering repeating code patterns. Code snippets are essentially templates that are created by you or the community to make entering repeating code patterns such as loops or conditional statements much faster. You may have noticed them before when the intellisense code completions popup menu shows, they can be identified with the square icon. I frequently write TypeScript so I commonly make use of the built in JavaScript snippets, an ES7 + React extension and some custom Jest snippets. I highly recommend the Snippets user guide on Visual Studio Codes documentation if you want to get started with this one!

Rename Symbol

This shorcut allows you to rename the function or variable your cursor is on. It will rename its definition and all of its references. On both MacOS and Windows the shortcut is F2.

Fast Imports with Quick Fix

Manually importing variables and functions can be time consuming, thankfully with the quick fix feature this becomes a lot quicker. When your cursor is on a line with an error or warning you can activate it with ⌘+. on MacOS or Ctrl+. on Windows. Be sure to fact check the import suggestions if you're dealing with a larger codebase that could have multiple definitions for the same variable or function. In these larger environments it may initially give you the wrong suggestion!

Refactoring

This feature allows you to move the highlighted code into a reusable variable or function. It can come in handy if you tend to just hack the code together initially then refactor and polish it before pushing it to your remote branch and getting peer reviews. On MacOS the shortcut is ⌘+⇧+R and for Windows they are Ctrl+Shift+R.

Move Line Up/Down

The move line up or down feature will do just that, move the line your cursor is on up or down. This also works if you highlight multiple lines too. I use this pretty often, because honestly I'm human and I don't always get the order of my code correct the first time. On MacOS the shortcuts are ⌥+↑/↓ and Windows they are Alt+↑/↓.

Go to Definition & Show References

If you're hovering a references to a variable or function the go to definition will do exactly that. Similarly, if you're hovering a variable or function declaration the show reference shortcut will show a menu of all the references if theirs multiple or go directly to the reference if theres just one. on MacOS the shortcuts are F12/⇧+F12 and Windows they are F12/Shift+F12.

These shortcuts are great but personally I find F12 to be a little far from my general hand placement on a keyboard so I opt to use ⌘/Ctrl+left click which I use frequently and works for both features.

Organize Imports

This shortcut will remove any unused imports, sort existing imports by file paths, and sort named imports as well. On MacOS, the shortcut is ⌥+⇧+O and Windows Alt+Shift+O.

This is a wonderful shortcut to save time cleaning up your imports before performing a commit if you're in the habit of using it, but you might prefer to edit your settings.json with the follow configuration so the IDE does it for you on save. The settings.json can be found by opening the command palette(MacOS & Windows: F1) and searching for it.

These shortcuts are just the top ones I frequently use or plan to use more of, but theres a plethora of keyboard shortcuts for Visual Studio Code. If you're looking to boost your efficiency within Visual Studio Code even further, they provide a cheatsheet for MacOS and Windows which can be good to keep handy.