Issues

See issues that are in progress

This blog will go over how to use Issues page in Haystack.

Recent Activity

Last 24hrs Activity

This view allows your to see all activity changes across Git & Jira for any issue.

You can understand majority of what has happened in the last 24 hours.

You can update the time frame to

  • Last 24 hours

  • Last 48 hours

  • Last 72 hours

  • Last 96 hours

This is particularly useful on Monday's when you want to understand what happened since Friday.

Note:

Activity Bubbles

Haystack combines both Jira & Git activity into a single activity bar. The more activities there are the bigger the bubble is.

You can hover over each bubble and see all the activity that has happened.

Bubble colors have meaning

  • Light Blue: Only Jira Activity

  • Dark Blue: Has at least one Git Activity

This allows you to see more intentful activities like Git commits and less intentful activities like Jira priority changes.

Note:

  • If you are using multiple version control systems like Github & Gitlab together, both of their activities will be shown as long as the Pull Requests are linked.

Time in Status

You can view both

  • Time in status: Time spent in that status (column)

  • Time in progress: Total time spent in-progress

These allow you to see if any issue stuck for a long period of time that might need your attention.

Filter by Member

Member filter allows you to see all the issues in that cycle.

Potential Risks

Risk sections allows you to easily filter across the risks you have selected.

Each risk is configurable

Once a risk is configured, you'll see a corresponding icon appearing next to issues which have this risk.

You can hover over the icons to see further details.

You can set alerts when an issue is above it's stuck threshold or when an SLA is at risk.

Progress Timeline

The timeline shows different for Kanban & Sprint teams.

  • Kanban: Shows Monday to Sunday

  • Sprint: Shows start of sprint to end of sprint

Kanban version is a more vanilla version of the Sprint Progress Timeline.

If you set capacity via settings, you will be able to see one more line in the graph called "Capacity" in the graph.

You can set alerts when the team goes over the set sprint capacity

Editable Fields

You can edit most field in the tables just by clicking of them.

The fields that are editable are

  • Issue Type

  • Priority

  • Storypoints

  • Assignee

View Issue Metadata

Clicking on any issue will bring up Issue Details side panels. This panel allows you to take a deeper dive into what's happening.

Customizable Views

Haystack allows you to customize your view. We'll go over each section one by one.

Update List Layout

Default layout is list.

Update Board Layout

You can select board layout to represent a scrum board.

Update Columns

You can group issues based on

  • Status Category (default)

  • Status

  • Epic

  • Assignee

  • Issue Type

Update Sort Order

You can sort the issues based on

  • Last Activity (default)

  • Priority

  • Match Jira

Note:

  • Match Jira option ensure the order is exact same as in Jira. This settings works for both Board & List layouts.

Update Display Properties

You can modify the metadata shown in the table.

The available options are

  • Issue Type

  • Priority

  • Assignee

  • Storypoints

  • Epics

  • Subtasks

  • Injected Tag

  • Labels

Property settings will effect metadata shown in preview modals like Last 24 hours.


FAQ

What data is shown in Active Issues page?

Active issue pages content changes based on your settings.

  1. Kanban: Shows all issues in your board based on your settings

  2. Sprint: Shows all issues in your sprint based on your settings.

Note: If an issue is in-progress but not in your sprint, Haystack will not show that issue.

The settings that effectives what's shown are

  1. Sprint Filter (only for sprint based boards)

Why do I see a different projects issue in my team?

Most likely case is you have Include non-team members work in Advanced Board Settings as enabled.

This settings ensures the data matches JIRA 100% by ignoring the "Team Member Settings" and showing everyone who contributed to that board.

If you think it doesn't look correct you can disable the setting and check if you still see any problems. If so, you'll need to check all settings that helps calculate what a team setting is.

There are 4 settings that effects a teams data.

Why do I see a different teams issue in my team?

Most likely case is you have Include non-team members work in Advanced Board Settings as enabled.

This settings ensures the data matches JIRA 100% by ignoring the "Team Member Settings" and showing everyone who contributed to that board.

If you think it doesn't look correct you can disable the setting and check if you still see any problems. If so, you'll need to check all settings that helps calculate what a team setting is.

There are 4 settings that effects a teams data.

How does Haystack know if a Pull Request is linked to an Issue?

Haystack links Pull Requests to Issues by using JIRA's referrence issue document.

How can I check which Pull Requests are linked to my issue?

You can click on any issue to see the Pull Requests clicked to them

How can I check which Pull Requests are not linked to any issue?

You can check this via creating a new report with the metric PRs unlinked.

If you click on any point in the graph, it'll show you the whole list of unlinked Pull Requests in the given segment.

Last updated