Website problem reports to the web team
Sentra 311 requests about the city website become Jira issues in the digital services project.
Jira Cloud from Atlassian is used by city IT, GIS and digital services teams to track projects, bugs and requests. Work lives as issues in projects with statuses, priorities and assignees.
SentraBridge creates and updates Jira issues and reads issues changed since the last run with JQL. Requests from other systems can land in a team's Jira project, and status can flow back. Issue data passes through without being stored.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Issues | list, read one | create, update | yes | Key, Summary, Status, Priority, Assignee, Updated… |
Sentra 311 requests about the city website become Jira issues in the digital services project.
Records that fail a flow's checks open a Jira issue for the data team with a summary of what failed.
When a Jira issue linked to a ServiceNow incident is resolved, the incident is updated.
Issues updated last week are counted by status and posted to the IT Teams channel.
Systems cities commonly connect with Jira, each with its own connector page.
Yes. Jira Cloud's REST API v3 lets apps search issues with JQL and create or update them, signed in with an email and API token.
Yes. A flow can create a Jira issue from a ServiceNow incident and write status back when the issue changes.
This connection targets Jira Cloud. A self-hosted Jira can be reached as a REST API, through the relay if it's inside the network.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.