Integration
Atlassian Jira &
Neelix Implementer

Managing Delivery and Strategy With Neelix Implementer and Jira Integration
The Purpose
- Calculate RAG status
- Enrich indicators with custom information
- Communicate cumulative progress
Stay In Sync
Seed data using jql query or list of projects. Update previously imported indicators with latest.
Stay Informed
Update dimensions; Update actual progress; Get properties for indicators; Calculate and update RAG status.
Flexible Connectors Without Admin Overheads
- Configure any number of connectors - all attributable to a person responsible for updates
- Configure connectors to multiple Jira domains - capability to bring vendors and partners into a cohesive ecosystem of indicators
- Easy to configure - no overheads on IT administrators whilst ensuring strong data access controls

Import and Update Seed Data
- Specify JQL and / or include list of projects
- Options to specify custom fields
- Inline customization
- Suggestions and capability to include additional dimensions
- Capability to update the data any number of times in the future to reflects changes in source Jira

Calculate Status Based On Source Data
- Three possible outcomes
- Update value of a property linked to an indicator
- Update status of an indicator (source data transformed into RAG and commentary)
- Update actual progress of an indicator used to track delivery
- Process a list of Jira records based on custom jql
- Get scalar (single) value
- Parse values within a nominated field of an array of issues
Layer Calculations for Determining Accurate Status
- Capability to configure multiple actions when calculating a RAG status for a given indicator
- Choose "average" or "worse" outcome choice

Access Controls
- All connectors are attributed to an "owner"
- user who is permitted access to your space in Neelix
- user who has access to your instance of Jira, as managed by your administrators
- Connection is governed by the API Token generated by owner - this ensures that the connection can only receive the amount of data permitted to the owner of the API token (user API Token is encrypted with 256-bit encryption)
Data Handling
- GET requests for data always request only the specific fields requested by the user.
- Received data attributes are parsed and discarded - the list of issues is never stored