Work tracking · Export
PYD ENTERPRISES and Jira
Turn every rule flagged for review into a Jira issue with source location, extracted logic and reviewer, so sign-off happens in the tracker your program already runs on.
Jira
Work tracking
1{2 "summary": "Review LNFEES-0087: late fee waived when grace days > 10",3 "issuetype": "Rule Review",4 "components": ["LOANS/FEES"],5 "labels": ["pyd", "rule-kind:eligibility", "flag:unreachable-branch"],6 "pydRuleId": "LNFEES-0087",7 "description": "Extracted: IF LN-GRACE-DAYS > 10 THEN fee = 0. Source: LNFEES01.cbl lines 412 to 431. Flag: branch unreachable under current JCL PARM; confirm whether it is still policy."8}
Rule review is work, so track it as work
PYD ENTERPRISES accounts for every executable path: it is extracted as a business rule, classified as plumbing, or flagged for review. The flagged set is where human judgment is needed: a rule that depends on an unresolved CALL target, a dead-looking branch that a production dataset might still reach, two copybooks that disagree about a field, an ELSE branch that charges a fee for unknown tier codes. On a large system that list runs to hundreds of items, and it needs owners, due dates and status like any other workstream.
The Jira integration creates one issue per flagged rule (or per decision, if you prefer to review a whole DMN table at once) in a project you nominate. The issue carries the rule ID, a plain-language statement of the extracted logic, the FEEL expression or formula, the source file and line range, and a link to the side-by-side review view in your PYD ENTERPRISES console.
How the sync behaves
PYD ENTERPRISES creates and updates issues through Jira's REST interface using a service account you create, with permission to create and edit issues in that project only. Mapping is configurable: issue type, components (we suggest one per legacy subsystem), labels for rule kind (calculation, eligibility, validation, routing) and a custom field for the PYD ENTERPRISES rule ID.
- When a later scan changes a rule's source lines or logic, PYD ENTERPRISES comments on the existing issue instead of opening a duplicate.
- When a reviewer resolves the issue, PYD ENTERPRISES reads the resolution on its next sync and records the sign-off (who and when) against the rule.
- Issues never contain more source than the line range under review, and you can switch excerpts off entirely.
Jira Data Center, Jira Cloud and CSV
With Jira Data Center inside your network, the sync stays inside your network. With Jira Cloud, the PYD ENTERPRISES service needs an egress rule to your Atlassian site, and you should decide with your security team whether code excerpts may appear in issue bodies. Air-gapped programs can export the review queue as a CSV file shaped for Jira's CSV importer and load it from an approved workstation.
FAQ
Jira questions.
Can we review a whole decision table in one issue instead of one issue per rule?
Yes. Choose decision-level grouping and PYD ENTERPRISES creates one issue per DMN decision with a checklist of its rules.
Does closing a Jira issue change the extracted rule?
Closing records sign-off. If the reviewer marks the rule as incorrect, it goes back to the review state in PYD ENTERPRISES with the reviewer's comment, and the analyst adjusts the classification there.
Will this flood our Jira with issues?
Only flagged rules become issues by default, and rescans update existing issues rather than creating new ones. You can also cap the sync to specific subsystems.
RELATED INTEGRATIONS
GitHubMirror GitHub or GitHub Enterprise Server repositories inside your VPC, scan a pinned commit, and return specifications to a review repository as pull requests.
GitLabClone self-managed GitLab projects inside your network, run PYD ENTERPRISES as a CI job on your own runners, and publish specs back as merge requests.
BitbucketIngest legacy repositories from Bitbucket Data Center or Bitbucket Cloud with read-only credentials, and return specification bundles as pull requests for review.
Azure DevOpsScan Azure Repos Git repositories and TFVC snapshots from Azure DevOps Server or Services, run scans from self-hosted pipeline agents, and export specs as pull requests.See the Jira flow on your own code.
Run PYD ENTERPRISES on 100,000 lines of COBOL or Java in your private VPC and review OpenAPI specs and DMN tables tomorrow.