StrataCom has provided IT service management consulting and business process analysis for a long list of Fortune 1000 clients since 1997. We recognize the individuality of your business processes and work diligently to maximize your investment. It is our firm belief that no company should have to change their business to fit a software package, ever. Share your vision with us and we’ll speak candidly with you about how StrataCom can make that vision a reality.

Contact

3523 45th Street South, Fargo, ND 58104

info@stratacominc.com

+1 -701-232-5697

My Teams Issues by StrataCom

My Teams Issues by StrataCom is a Jira dashboard gadget that helps users see work assigned to the Atlassian Teams they belong to.

The gadget looks up the current viewer’s Atlassian Teams, builds a Jira issue search from those teams, and displays matching issues in a configurable dashboard table. It is designed for teams that use Jira dashboards to monitor open work, incidents, service requests, or other team-assigned issues.

Who This App Is For

This app is useful for Jira Cloud teams that:

How It Works

When the gadget loads, it:

  1. Identifies the current Jira user viewing the dashboard.
  2. Looks up the Atlassian Teams that user belongs to.
  3. Builds a Jira query using the configured Team field.
  4. Applies any additional JQL or saved Jira filter configured for the gadget.
  5. Displays the matching Jira issues in a sortable dashboard table.

The gadget does not require users to refresh a team cache, enter an API token, or manually maintain team membership data.

What Users See

The dashboard gadget displays a table of Jira issues assigned to the viewer’s Atlassian Teams.

Depending on the gadget configuration, columns can include fields such as:

Issue keys open the related Jira issue so users can move directly from the dashboard to the work item.

Jira Permissions Still Apply

The gadget respects Jira permissions for issue data. Users only see Jira issues that they already have permission to view in Jira.

If a user belongs to an Atlassian Team but does not have permission to view a matching issue, that issue will not appear for them in the gadget.

Adding The Gadget To A Dashboard

To add the gadget:

  1. Open the Jira dashboard where the gadget should appear.
  2. Select Add gadget.
  3. Search for My Teams Issues by StrataCom.
  4. Add the gadget to the dashboard.
  5. Open the gadget configuration to choose fields, filters, and display options.

You must have permission to edit the Jira dashboard before you can add or configure gadgets.

Gadget Configuration

Team Field

The Team field tells the gadget which Jira issue field stores the assigned Atlassian Team.

Many Jira sites can use the default Jira Team field. Some sites use a custom Team field instead. If the gadget does not return the expected issues, confirm that the selected Team field matches the field used on your Jira issues.

Grid Fields

Grid fields control which columns appear in the table.

The field picker can be used to select Jira fields without typing field names manually. Selected fields can also be reordered so the dashboard table appears in the most useful left-to-right order.

Additional JQL

Additional JQL narrows the results beyond team membership.

Examples:

statusCategory != Done
project = ITSM
issuetype in ("Incident", "Service Request")

The gadget combines this JQL with the viewer’s team query.

Saved Jira Filter

The gadget can also append JQL from a saved Jira filter.

This is useful when your organization already maintains standard filters for open incidents, active service requests, escalations, or other recurring views.

If the selected filter contains an ORDER BY clause, the gadget ignores that ordering and uses the gadget’s own ordering setting instead.

Order By

The Order By setting controls how Jira sorts the results.

Common examples include:

updated DESC
priority DESC, updated DESC
created DESC

Max Results

Max Results controls how many issues the gadget requests from Jira.

Smaller result sets usually load faster. If the gadget is slow, use more specific JQL or reduce the maximum result count.

Records Per Page

Records Per Page controls how many rows appear on each page of the dashboard table.

This setting changes the table display only. It does not change how many issues are requested from Jira.

Troubleshooting

I See A Message That The Viewer Is Not In Any Cached Teams

This means the app did not find any Atlassian Teams for the current viewer.

Confirm that the user is a member of at least one Atlassian Team. This app uses Atlassian Teams, not Jira groups.

No Issues Are Displayed

If the gadget loads but no issues appear, check the following:

The Team Column Is Blank

If issues are returned but the Team column is blank, the selected display column may not be the same field used for the team query.

Edit the gadget and confirm both:

Duplicate Team Fields Appear In The Picker

Some Jira sites have multiple fields with similar names, such as Team, Teams, Project Team, or Assignment Team.

When this happens, choose the field that matches the Jira issue field your organization uses for team assignment. Custom fields may appear with their Jira field ID to help distinguish them.

Asset Or Service Fields Show Unexpected Values

The gadget can resolve supported Jira Service Management Assets fields to more readable names. If an Assets field does not display as expected, confirm that the field is included in the grid configuration and that the app has the required Jira Service Management Assets permission.

Data And Security

My Teams Issues by StrataCom runs on Atlassian Forge and uses Atlassian APIs to look up teams and Jira issues.

The app does not require an external API token for team lookup and does not maintain a persistent team membership cache. Team membership is resolved when the gadget loads.

Jira issue visibility remains controlled by Jira permissions.

Support

For help, contact your Jira administrator or use the support channel listed on the Atlassian Marketplace app listing.

When reporting an issue, include: