Create advanced Works with: Any AI

Project Risk and Issue Log Built From Jira Tickets

Table output Has example

• 🧭 Jira

Create a risk register from tickets and comments.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Build a risk and issue log from these Jira tickets and comments: [TICKETS_AND_COMMENTS]. Project context: [PROJECT_CONTEXT]. Delivery date: [DELIVERY_DATE].

Separate risks (might happen) from issues (have happened). For each, give the description in cause-event-effect form, evidence quoted from the tickets, likelihood and impact from 1 to 5, the score as the product, an owner placeholder, mitigation, a trigger to watch, and a review date. Rank by score and mark any risk with impact 5 regardless of score. Do not treat a single comment as proof of a risk, and state assumptions clearly.

Output a table I can paste into Confluence, then a list of Jira issues to create for the top five mitigations (summary and description). Example row (invented): risk R1, payment provider test accounts delayed, evidence quoted from a ticket comment, likelihood 4, impact 4, score 16. Keep each risk to one line of cause, event and effect so the table stays readable. If the tickets give too little evidence for a score, mark the score as provisional and write the question that would settle it.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented rows. Risk R1: payment provider test accounts delayed; evidence quote from ticket comment; likelihood 4, impact 5, score 20; mitigation: request accounts this week and mock the provider; trigger: no account by the 20th; review date the 22nd. Risk R2: single developer knows the export code; likelihood 3, impact 3, score 9. Issue I1: staging down for 2 days. Ranking by score: R1, R2. Impact 5 flagged regardless. Top five mitigations become Jira issues labelled risk-mitigation. Review rhythm: the log is read in the weekly project meeting for 10 minutes; any score above 15 has a named owner and a date.

• jira