Shorter Loop API Documentation
API ReferencesRelease NotesHelp CenterKnowledge Base
API ReferencesRelease NotesHelp CenterKnowledge Base
Sign In
  1. Getting started
  • Getting started
    • Welcome to the Shorter Loop API Portal
    • Authentication
    • Base URL
    • 2 way Jira Integration
    • Create webhook in Shorter Loop
  • Metrics
    • Create a Key Performance Indicator (KPI)
      POST
    • Update the Key Performance Indicator (KPI)
      PUT
    • Retrieve KPIs not linked to specific product backlog items
      GET
    • Insert KPI's records (Body JSON Payload)
      POST
    • Insert KPI's records (Upload CSV)
      POST
    • Insert KPI's records (Upload JSON)
      POST
  • Idea manager
    • Feedback Collection
      • Create idea and issue
      • Retrieves a list of categories
      • Modify feedback item
      • Removes a feedback item
      • Upvote or downvote a work item
      • Retrieve a feedback item
      • Get comments for a feedback item.
      • Reply to a comment
      • Modify a comment
      • Bulk create feedback items: CSV and JSON
    • Segments
      • Retrieves a list of segments without users
      • Create segment
      • Modify a segment
      • Removes a segment
      • Bulk create users to a segment
      • Manage user segments: move or remove
      • Retrieve segments with users
      • Retrieve segment with users
      • Import Users (CSV/JSON)
      • Sending email to segment members
      • Sending email to selected idm members
    • Bulk create idea manager members
      POST
    • Import Users (CSV/JSON) in IDM
      POST
    • Bulk re-invite in IDM
      PUT
  • Backlog Management
    • Epics
      • Create a new epic
      • Modify an epic
      • Retrieve details of the epic
      • Removes the epic
    • Features
      • Create a new feature
      • Modify a feature
      • Retrieve details of the feature
      • Removes the feature
    • User stories
      • Create a new user story
      • Modify a user story
      • Retrieve user story
      • Removes the user story
    • Assets
      • Attaches files to the workitem
      • Removes an asset
      • Retrieve attachments for the backlog workitem with ID
    • Product Tags
      • Retrieves tags for initiative
    • Teams
      • Get teams and members for product
    • Personas
      • Retrieve personas associated with initiative
    • Get whole backlog tree
      GET
  • Strategy Board
    • Experiment
      • Create a new experiemnt variant
    • Solutions
      • Versions
        • Storymap versions api documentation
        • Create a version
        • Update version
        • Removes a version
        • Retrieve versions
      • Get all storymaps for solution
  • Persona Board V2
    • Segments
      • Permanently deletes a segment
      • Creates a new option
      • Retrieve a list of segments
      • Retrieve a segment
      • Create a segment
      • Removes a segment
      • Removes a segment option
      • Detaches a segment from the persona
      • Update segment option
    • Custom fields
      • Removes a custom field
      • Retrieve a list of custom fields
      • Retrieve a custom field
      • Create a custom field
      • Removes a custom field option
      • Detaches a custom field from persona
      • Retrieve custom fields excluding persona
      • Creates a new option
      • Permanently deletes a custom field
      • Update custom field
      • Update custom field option
      • Attach a custom field to a persona
    • Create opportunities from summary
    • Retrieve notes
    • Retrieve persona
    • Retrieve experiments for Persona
    • Create
    • Retrieve
  • DocsHub
    • Retrieve categories with templates
    • Retrieve a template based on category
    • Create copy of template while using template
  1. Getting started

2 way Jira Integration

Sync seamlessly both ways—push work items to Jira or import Jira tickets into Shorter Loop.

Keep your Jira projects up to date by enabling Jira Sync while you're exploring or switching to Shorter Loop.

Use CSV or APIs to perform a one-time import from Jira into Shorter Loop. Refer.: https://developer.shorterloop.com

Jira-SL.png

Overview: Flexible Transition Paths to Shorter Loop

Teams adopt Shorter Loop in ways that best fit their workflows. Some opt for an immediate switch, importing all existing issues at once. Others prefer a gradual adoption, starting with a small team to evaluate the platform's fit.

To support a phased transition, Shorter Loop offers 2-Way Jira Sync. This feature enables seamless integration between Jira projects and Shorter Loop teams, ensuring that new issues created in either system are automatically synchronized. This bidirectional sync maintains consistency across platforms, allowing teams to collaborate effectively during the transition period.

Navigate to Integrations → Apps Section and click on Link from Jira.

Prerequisites & Permissions

  • ADMINISTER permission
    The Jira account you use to create the API token must have the GLOBAL ADMINISTER permission in Jira. This is required so Shorter Loop can register webhooks.

    • Once setup is complete, you can revoke that permission in Jira without breaking the integration.

    • If you don’t want to assign a Shorter Loop seat to this admin user or store that permission in Shorter Loop, see our FAQ for alternatives.

  • API Token lifespan
    Atlassian tokens default to 7 days. When you generate yours, set its expiration to 1 year to avoid frequent renewals.

How to Setup?

image.png

  1. Open the Link dialog

    • In Shorter Loop, go to Integrations → Apps, then click Link from Jira.

Link-jira-account.png

  1. Generate or locate your API token

    • In Jira: Settings → Security → API tokens → Create token (or copy an existing one).

    • On creation, choose an expiration of 12 months.

  2. Collect your credentials

    • API Token

    • Email for your Jira user

    • Jira Hostname (e.g. yourcompany.atlassian.net)

  3. Authenticate

    • In the Shorter Loop dialog, paste API Token, Email, and Hostname, then click Link.

  4. Confirmation

    • Success: You’ll see a green “Linked successfully” banner.

    • Error: A red message will explain what went wrong (invalid token, mistyped hostname, etc).

  5. Import of Projects

    • Immediately after linking, Shorter Loop imports every Jira project in your instance.

Reminder: Imported projects are not yet connected with Shorter Loop—no sync is active until you connect them to a team.

imported-jira-projects.png

Step 2 — Connect Projects to Teams

image.png
Each Jira project must be paired with exactly one Shorter Loop team. Follow these steps:

  1. Ensure you have at least one team

    • If none exist, you’ll see: “You need to create at least one team to integrate with Jira.”

    • Head to Teams → Create Team, then return here.

  2. Start the connection flow

    • Under Integrations → Apps, locate your imported Jira projects.

    • Click Connect on the project you want to sync.

Connect-project.png

Step 1: Choose a Team

  • A three-step wizard appears.

  • Team dropdown lists only teams not already linked to another project.

  • If your current header-dropdown team is unlinked, it will be pre-selected.

  • Click Continue (or Back to cancel).

Select-team.png

Step 2: Select Work-Item Types

  • Pick which types of issues you want in sync (e.g. bugs, tasks, epics).

  • Click Continue.

Workitem mapping.png

Step 3: Map Fields

  • Align Jira fields (summary, description, status, etc.) with Shorter Loop fields.

  • Click Continue to finalize.

jira-workitem-mapping.png

Automatic Sync Activation

  • The moment you finish Step 3, Shorter Loop creates a Jira webhook and begins bi-directional sync:

    • Push: New or updated work items in Shorter Loop go to the respective Jira Project.

    • Pull: New or updated issues in Jira appear in Shorter Loop's team backlog.

Note: Only those Shorter Loop workitems are pushed to jira which has a Team assigned.

connected.pngwebhook.png

Additionally, a webhook is also created in Shorter Loop.

webhook-sl.png

shorterloopId & Cleanup on Disconnection

image.png

Duplication prevention

A custom field named shorterloopId (this is our Smart key) is created automatically by Shorter Loop in Jira.

Update vs. create

If an incoming issues carries a shorterloopId, we will update the existing work item; if not, it will create a new one.

Automatic field creation

During the “Link from Jira” step, Shorter Loop automatically provisions the shorterloopId custom field in your Jira instance.

IMPORTANT: Team-managed projects

For team-managed Jira projects, you must manually add the shorterloopId field to each work type in Jira:

  1. Go to Jira Project Settings → Fields → Add Field

  2. Search for shorterloopId, select it, and click Add

add-field.png

  1. Switch to Work Types in Project Settings

  2. Under each work type’s Text Fields, click shorterloopId to include it (You need to do it for all the work types you have in Jira)

adding-to-epic.png

  1. Save changes

Note: If this manual addition is not performed, there are chances of duplicate items in jira and Shorter Loop on each re-connection.

Disconnect cleanup

  • When a user disconnects a Jira project, Shorter Loop removes all Jira metadata from the associated work items.

  • If a user fully unlinks from Jira, Shorter Loop deletes the Jira project connection and wipes out all Jira details from every synced work item.

  • Removing the jira connected Shorter Loop Team will automatically disconnected the jira project.

Unit test cases

#ScenarioPreconditionsTest StepsExpected Result
TC01Link Shorter Loop to JiraUser has Shorter Loop admin account; Jira user has GLOBAL ADMINISTER permission and a valid API token1. In Shorter Loop, navigate to Integrations > Apps and click Link from Jira. 2. In Jira, generate or copy your API token (in Settings > Security > API Tokens) and note your Jira email and host URL. 3. In the Shorter Loop link dialog, enter the API token, Jira email, and hostname, then click Link. 4. Verify that a green “Linked successfully” banner appears, indicating the integration was established.
TC02Import Jira projects into Shorter LoopJira account has been successfully linked to Shorter Loop (from TC01)1. Immediately after linking, go to Integrations > Apps in Shorter Loop. 2. Verify that all Jira projects from the linked Jira instance are listed under “Imported Jira Projects.” 3. If teams do not exist, confirm that a message appears instructing to create a team for integration.
TC03Connect a Jira project to a Shorter Loop teamAt least one Shorter Loop team exists; Jira project has been imported (from TC02)1. Ensure at least one Shorter Loop team is created (in Teams > Create Team if needed). 2. In Shorter Loop, go to Integrations > Apps, locate the desired imported Jira project, and click Connect. 3. In the three-step connection wizard, select the Shorter Loop team to sync and click Continue. 4. On the “Select Work-Item Types” step, choose which Jira issue types (e.g. Epics, Bugs, Tasks) to sync and click Continue. 5. On “Map Fields” step, align the Jira fields (summary, description, status, etc.) with Shorter Loop fields, then click Continue to finalize. 6. Confirm that a Jira webhook is created and the bidirectional sync becomes active.
TC04Push a Shorter Loop work item to JiraJira project is connected to a Shorter Loop team with active sync (from TC03)1. In Shorter Loop, within the connected team backlog, create a new work item (e.g. a User Story) and fill in required fields (title, description, etc.). 2. Save the new work item in Shorter Loop. 3. In the linked Jira project, verify that a new issue has been created with matching details (such as summary and description) from the Shorter Loop work item. It must have a Shorter Loop Url as remote url in Jira.
TC05Pull a Jira issue into Shorter LoopJira project is connected to a Shorter Loop team with active sync (from TC03)1. In Jira, create a new issue in the connected project using one of the selected issue types. 2. After saving the issue in Jira, go to the Shorter Loop team backlog connected to that project. 3. Verify that a corresponding work item has appeared in Shorter Loop with matching fields (title, description, etc.) as the Jira issue.
TC06ShorterLoop integration installation should register a new webhook in Jira to send events to ShorterLoop.- User has Administer Jira (global) permission - ShorterLoop integration is available and linked to the Jira instance.1. Log in to Jira as an administrator. 2. Install or enable the ShorterLoop Jira integration (e.g., via Atlassian Marketplace). 3. Navigate to Jira Administration > System > Webhooks. 4. Verify that a new webhook is listed with the ShorterLoop callback URL and the correct event triggers configured.
TC07Attempting to register a Jira webhook without required permissions should fail.- User does not have Administer Jira (global) permission - ShorterLoop integration is set to register a webhook1. Log in to Jira as a non-administrator user (no Administer Jira permission). 2. Install or enable the ShorterLoop integration in Jira. 3. Attempt to create or view webhooks under Jira Administration > System > Webhooks. 4. Confirm that no new ShorterLoop webhook is present and check for an access denied error.
TC08When a Jira issue event (e.g., issue created or updated) occurs, the registered webhook should send data to ShorterLoop.- A valid ShorterLoop webhook exists in Jira (from TC06). - A test issue is available in the integrated Jira project.1. Perform an action in Jira (e.g., create or update an issue in the integrated project). 2. Monitor the ShorterLoop integration or its logs for receipt of the webhook event payload. 3. Verify that ShorterLoop receives the correct data corresponding to the issue event.
TC09Integration should automatically create a "ShorterLoop ID" issue field in a company-managed Jira project to store mapping IDs.- User has Administer Jira permission (to create custom fields). - ShorterLoop integration is installed and connected. - No existing "ShorterLoop ID" field in Jira.1. In the ShorterLoop integration settings, select a company-managed Jira project for synchronization. 2. Trigger the integration setup that provisions custom fields. 3. Go to Jira Administration > Issues > Custom fields and locate the new field named "ShorterLoop ID". 4. Verify that this field is attached to the appropriate issue screens/types for the project.
TC10Integration on a team-managed project should prompt the user to manually create the ShorterLoop ID field, since team-managed projects cannot use custom fields from company-managed projects.- Jira project type is team-managed (next-gen). - ShorterLoop integration is installed and attempting to provision fields.1. Install or connect the ShorterLoop integration and select a team-managed project. 2. Observe that the integration detects the project type and provides instructions to manually add a new field "ShorterLoop ID" to the project. 3. Navigate to Project Settings → Issue Types → (relevant issue type) → Add field, and create the "ShorterLoop ID" field.
TC11If the ShorterLoop ID field is not configured in a team-managed project, integration features (e.g., syncing IDs) should fail or produce an error, since custom fields from company-managed projects cannot be used in team-managed projects.- Jira project is team-managed. - Integration is installed but the "ShorterLoop ID" field has not been created.1. Attempt to use the ShorterLoop integration features (e.g., synchronize issues) without creating the "ShorterLoop ID" field in the team-managed project. 2. Observe the integration’s response or error handling (e.g., check for warnings in the integration UI or logs). 3. Verify that, without the field, no ID mapping occurs for team-managed issues.
TC12Integration encounters an expired Jira API token and should handle authentication failures.- ShorterLoop integration is using a Jira API token or OAuth credentials that are expired or revoked. - Access token was valid previously but now beyond its valid period.1. Obtain or configure a Jira API access token that has expired (simulate by using a revoked token or setting its expiry date in the past). 2. Attempt to synchronize data (e.g., import or update a Jira issue) through the ShorterLoop integration. 3. Observe that the Jira API request fails with an authentication error (e.g., HTTP 401 Unauthorized). 4. Verify that the integration logs an error or notifies the user that re-authentication or token renewal is required.
TC13Integration operates normally when the Jira API token is valid and not expired.- ShorterLoop integration has a valid Jira API token (within its expiry date). - Permissions are correctly granted.1. Ensure the Jira API token for ShorterLoop integration is active and has not expired. 2. Perform a standard integration action (e.g., sync or update a Jira issue from ShorterLoop). 3. Confirm that the request succeeds and the issue is properly synchronized without errors.
TC14Uninstalling the ShorterLoop integration should remove the Jira webhook that was created.- Integration is currently installed with a webhook active.- Jira Administrator permission available to verify webhooks.1. In Jira, uninstall or disable the ShorterLoop app, or in ShorterLoop settings, disconnect the Jira integration. 2. Verify that the Atlassian Connect 'uninstalled' lifecycle callback is triggered (e.g., check integration logs). 3. Go to Jira Administration > System > Webhooks and confirm that the ShorterLoop webhook is no longer listed.
TC15Uninstalling the integration should remove any custom fields (e.g., "ShorterLoop ID") that were created by the integration.- Integration is installed and has created a "ShorterLoop ID" field in Jira. - Jira Administrator permission available.1. Uninstall or disconnect the ShorterLoop integration from Jira. 2. In Jira Administration > Issues > Custom fields, search for "ShorterLoop ID". 3. Confirm that the custom field has been deleted (or disabled) as part of the cleanup process.
TC16Attempting to provision the ShorterLoop ID field without Jira admin rights should fail.- User lacks the Jira global Administer Jira permission. - ShorterLoop integration is installed.1. Log in to Jira as a non-administrator user. 2. Initiate the ShorterLoop integration setup that creates the custom field. 3. Observe that Jira denies the creation of the "ShorterLoop ID" field (e.g., no new field appears, an error is shown). 4. Verify that the integration reports the failure or that the field is not created.
TC17New Shorter Loop work item is automatically pushed to the linked Jira project.- Shorter Loop account is linked to Jira. - A Jira project is connected to a Shorter Loop team (field mappings are configured). - The work-item type is included in sync.1. In Shorter Loop, create a new work item and assign it to the connected team. 2. Ensure all required fields (e.g., summary, description) are filled out. 3. Wait for synchronization to occur, then open the linked Jira project in Jira. 4. Verify that a new issue has been created in Jira with details matching the Shorter Loop work item.
TC18New Jira issue is automatically pulled into Shorter Loop backlog.- Shorter Loop account is linked to Jira. - A Jira project is connected to a Shorter Loop team (field mappings are configured).1. In Jira, create a new issue in the connected project of a type mapped to Shorter Loop. 2. Fill in required fields (summary, description, etc.) and save the issue. 3. In Shorter Loop, navigate to the corresponding team backlog and refresh. 4. Verify that the new issue appears as a work item in Shorter Loop with matching details from Jira.
TC18New Jira issue is automatically pulled into Shorter Loop backlog.- Shorter Loop account is linked to Jira. - A Jira project is connected to a Shorter Loop team (field mappings are configured).1. In Jira, create a new issue in the connected project of a type mapped to Shorter Loop. 2. Fill in required fields (summary, description, etc.) and save the issue. 3. In Shorter Loop, navigate to the corresponding team backlog and refresh. 4. Verify that the new issue appears as a work item in Shorter Loop with matching details from Jira.
TC19Updating a Shorter Loop work item updates the corresponding Jira issue.- A Shorter Loop work item already exists and is synced with a Jira issue. - Shorter Loop is linked to the correct Jira project.1. In Shorter Loop, open an existing synced work item. 2. Modify one or more fields (e.g., title, description, status) in the Shorter Loop work item. 3. Save the changes and wait for synchronization. 4. In Jira, open the corresponding issue in the connected project. 5. Verify that the changes made in Shorter Loop are reflected in the Jira issue.
TC20Updating a Jira issue updates the corresponding Shorter Loop work item.- A Jira issue already exists and is synced with a Shorter Loop work item. - Shorter Loop is linked to the correct Jira project.1. In Jira, open an existing synced issue for the connected project. 2. Modify one or more fields (e.g., summary, description, status) in the Jira issue. 3. Save the changes and wait for synchronization. 4. In Shorter Loop, refresh the team backlog and locate the corresponding work item. 5. Verify that the changes made in Jira are reflected in the Shorter Loop work item.
TC21Shorter Loop work items without a team assignment are not pushed to Jira.- Shorter Loop account is linked to Jira. - A Jira project is connected to a Shorter Loop team (field mappings are configured).1. In Shorter Loop, create a new work item but DO NOT assign it to any team. 2. Fill in required fields (summary, description, etc.) and save the work item. 3. Wait for a synchronization interval. 4. Verify that no new issue is created in the connected Jira project for this work item.
TC22Incoming Jira issue with an existing shorterloopId updates the existing Shorter Loop work item.- A Shorter Loop work item and its corresponding Jira issue already exist (so a valid shorterloopId is established). - The shorterloopId custom field exists in Jira.1. Identify the shorterloopId value of an existing synced Shorter Loop work item (from its Jira issue). 2. In Jira, create a new issue in the connected project and manually set its shorterloopId field to that value. 3. Modify another field in the new Jira issue (e.g., summary or description) and save. 4. Wait for synchronization to occur. 5. In Shorter Loop, open the work item with that shorterloopId. 6. Verify that the existing Shorter Loop work item is updated with the changes from the new Jira issue, and no duplicate work item is created.
TC23Incoming Jira issue without a shorterloopId creates a new Shorter Loop work item.- Shorter Loop account is linked to Jira. - A Jira project is connected to a Shorter Loop team (field mappings are configured).1. In Jira, create a new issue in the connected project without specifying any shorterloopId value. 2. Fill in required fields and save the issue. 3. Wait for synchronization. 4. In Shorter Loop, refresh the team backlog. 5. Verify that a new work item has been created in Shorter Loop for this Jira issue (indicating creation rather than update).
TC24shorterloopId custom field is automatically created in Jira after linking.- The Shorter Loop Jira integration has just been completed (Jira account linked to Shorter Loop).1. In Shorter Loop, complete the process of linking the Jira account (enter credentials and confirm link). 2. In Jira administration, navigate to Custom Fields. 3. Verify that a new custom field named shorterloopId has been created (as a text or ID field). 4. Ensure the field is available for the issue types in the connected project (especially for non-team-managed projects, where it is auto-added).
TC25Without manually adding shorterloopId in a team-managed project, duplicates appear on reconnect.- A team-managed Jira project is connected to a Shorter Loop team. - The shorterloopId field has NOT been manually added to all work types in Jira.1. In Shorter Loop, ensure the team-managed project is connected and has been synced at least once. 2. Disconnect the Jira project from Shorter Loop (stop the sync). 3. Reconnect the same Jira project to the same Shorter Loop team again. 4. Wait for synchronization. 5. Verify that duplicate entries appear (for example, two Shorter Loop items or Jira issues for the same work items) due to the missing shorterloopId field.
TC26After adding shorterloopId field manually in a team-managed project, reconnection creates no duplicates.- A team-managed Jira project is connected to a Shorter Loop team. - The shorterloopId field has been manually added to all relevant work types in that Jira project.1. In Jira, go to the project settings for the team-managed project and add the shorterloopId custom field to each issue type as required. 2. In Shorter Loop, disconnect the Jira project (if currently connected) and then reconnect it to the same team again. 3. Wait for synchronization. 4. Verify that after reconnection only one Shorter Loop work item exists per Jira issue and no duplicates are created.
TC27Disconnecting a Jira project removes Jira metadata from Shorter Loop work items.- A Jira project is connected to a Shorter Loop team. - Several work items have been synced (so they contain Jira issue keys/links).1. In Shorter Loop, disconnect the Jira project from the team (turn off or remove the sync connection). 2. In Shorter Loop, open each previously synced work item in that team’s backlog. 3. Verify that all Jira-related fields (such as the issue key, links, or any Jira metadata) have been cleared or removed from those work items.
TC28Unlinking the Jira integration deletes project connections and clears all Jira details.- Shorter Loop is linked to a Jira account with one or more connected projects. - Work items have been synced between Shorter Loop and those Jira projects.1. In Shorter Loop integration settings, perform a full unlink/remove of the Jira account (disconnect the Jira integration entirely). 2. Confirm that all project connections to Jira are removed (no connected projects remain). 3. In Shorter Loop, inspect all previously synced work items across teams. 4. Verify that no Jira information (issue keys, links, etc.) remains in any work item after the unlink operation.
TC29Deleting a Shorter Loop team auto-disconnects its linked Jira project.- A Shorter Loop team exists that is connected to a Jira project.1. In Shorter Loop, delete/remove the team that is connected to the Jira project. 2. Check the integrations or projects list in Shorter Loop. 3. Verify that the Jira project that was linked to the deleted team is now disconnected (no longer appears as connected to any team). 4. Optionally, verify that any work items of the deleted team no longer show Jira metadata.
TC30One-time import from Jira to Shorter Loop using a CSV file.- A Jira project with issues exists. - A CSV file with exported Jira issues is prepared. - Shorter Loop account is ready to import issues.1. Export the desired issues from the Jira project into a CSV file (including fields like summary, description, etc.). 2. In Shorter Loop, navigate to the import or integrations section for Jira. 3. Upload or select the CSV file containing the Jira issue data. 4. Map the CSV columns to the corresponding Shorter Loop fields as needed. 5. Execute the import process. 6. After import completes, refresh the appropriate Shorter Loop team backlog. 7. Verify that all issues from the CSV have been added as new work items in Shorter Loop with correct details.
TC31One-time import from Jira to Shorter Loop using API.- A Jira project with issues exists. - Export CSV1. Import CSV in Shorter Loop 2. Verify every items from CSV is added in product backlog. 3. In Shorter Loop, refresh the relevant team backlog after the import is processed.
TC31Assigning a team to a Shorter Loop work item pushes it to the corresponding Jira project’s backlog.- Shorter Loop account is linked to Jira. - A Jira project is connected to a Shorter Loop team (with field mappings configured). - The work item exists in Shorter Loop but is not yet assigned to any team.1. In Shorter Loop, open an existing work item that is not assigned to any team. 2. Assign it to a team that is connected to a Jira project. 3. Wait for synchronization to complete. 4. Open the linked Jira project in Jira. 5. Verify that a new issue corresponding to the work item appears in the Jira backlog of the assigned team's project.A new Jira issue is created in the correct Jira project's backlog with data from the Shorter Loop work item.
TC32Webhook is created only after a Jira project is connected to a Shorter Loop team, not just on linking.- Jira account is linked to Shorter Loop via Product Integrations → Apps. - Jira projects are successfully imported. - No Jira project is yet connected to any Shorter Loop team.1. Link Jira account in Shorter Loop and observe the imported projects. 2. Do not connect any Jira project to a team yet. 3. Go to Jira → System → Webhooks. 4. Verify no webhook has been created. 5. Now, in Shorter Loop, connect one imported Jira project to a team using the integration wizard (Team → Work Item Types → Field Mapping). 6. Return to Jira → System → Webhooks.7. Verify that the webhook has now been created.Webhook is not created immediately after linking Jira.Webhook is created only after a Jira project is connected to a team in Shorter Loop.
TC33Unassigning a team from a work item should remove the Jira externalKey.- Jira is connected and synced with Shorter Loop. - A work item in Shorter Loop has a team assigned and is synced to a Jira project (has a valid externalKey).1. Go to the synced work item in Shorter Loop. 2. Unassign the team from the work item. 3. Save the work item. 4. Open the work item details again and inspect the metadata or database (if applicable).The externalKey (linked Jira issue ID) should be removed from the work item after the team is unassigned. The work item is no longer synced with Jira.
TC34Prevent multiple SL teams from connecting to the same Jira projectJira project can only be paired with one SL team. Prevent conflicts.
TC35Data privacy on token sharingMask API tokens when entered and stored.
TC36Re-assigning a team to work item triggers re-push to JiraIf work item had lost sync due to unassignment, re-assigning team should re-create/update in Jira.
Modified at 2025-05-27 07:40:40
Previous
Base URL
Next
Create webhook in Shorter Loop
Built with