Impact on Jira when connected to the piplanning app

Owned by admin (Unlicensed)
Last updated: Nov 22, 2022 by Dominique Burnand

Requirements to get the piplanning app connected to your Jira

  • Jira Cloud, Server or Data-center
  • The REST-API must be accessible (via basic-auth or OAuth)
  • In the Project you wan to have synced you will need at least the following permissions:
    • CREATE_ISSUES
    • DELETE_ISSUES (optional)
    • EDIT_ISSUES
    • LINK_ISSUES
    • MANAGE_SPRINTS_PERMISSION (optional)
    • BROWSE_PROJECTS
    • VIEW_READONLY_WORKFLOW
    • CLOSE_ISSUES (Optional)
    • RESOLVE_ISSUES (Optional)
    • TRANSITION_ISSUES (Optional)
  • Our server needs to be reachable on Port 443 by your Jira (webhook)

What the app will pull from your Jira:

  • Issue-types, link-types
  • Projects and board meta data
  • Issues of the projects you configured

What the app will push to your Jira:

  • Create, alter or delete issues in the projects you configured
  • Create or remove links in the projects you configured
  • Create new sprints (if you request that from the app)

How you can further limit the access of the piplaning app to your jira:

  • Give the user with which you setup the connection to Jira only the privileges he needs.
  • If you do not want that the app can delete anything in Jira, you can remove that permission on the user
  • Set a JQL filter in the webhook: This will then only post updates from Jira to the piplanning app matching that filter.

What size of traffic do we need to expect?

  • Whenever an update to a sticky is completed (and there is actually a change made concerning the ALM tool), the piplanning app will issue a request against it.
  • When a user / admin re-syncs a board or a session, we will query the ALM tool for issue-types, statuses, boards, sprints and issues.
  • Depending on the filtering you restricts on webhooks, there will be more or less request from your ALM to the piplanning app.

The information we will store on our server which is coming from your Jira

Also check out Field mapping piplanning app / Jira

Metadata:

  • Project, Sprint and Board id's
  • Issue-types
  • Fields-types
  • Links between issues
  • Issue-key of issues synced to the app

User-data:

  • Of issues synced to the app (are visible in the app):
    • Summary
    • Story-points value
    • Chosen numeric field (WSJF) value

Personally identifiable information (PII)

  • email address
  • username