NASA - Not Another Standup AppNASA - Not Another Standup App
Try For Free

Post-Meeting Automation

Transform your meeting outcomes into immediate action by automatically triggering Jira workflows when meetings end.

Overview

Post-Meeting Automation connects NASA to your Jira Automation (Confluence Automation) rules through webhooks, enabling automatic task creation, assignment changes, and workflow transitions based on meeting decisions.

Key Capabilities

Automated Task Creation

Create Jira issues automatically from text items from meetings, including all comments and context.

Smart Assignment

Automatically assign work items to meeting participants based on configurable rules and conditions.

Comment Synchronization

Transfer meeting notes and decisions directly to Jira issues as comments, maintaining complete context.

Workflow Automation

Trigger status transitions, sprint assignments, and custom field updates when meetings end.

How It Works

  1. Configure Automation Rules - Set up rules in NASA Settings under each agenda question

  2. Link to Jira - Connect rules to Jira Automation via webhook URLs

  3. End Meeting - NASA sends payloads to trigger your Jira rules

  4. Automatic Execution - Jira processes the rules and updates issues

Supported Actions

For Text Items

  • Create new Jira issues from text items

  • Include concatenated comments as issue descriptions

  • Auto-assign to meeting participants

For Work Items

  • Update assignee based on meeting decisions

  • Add meeting comments to existing issues

  • Trigger workflow transitions

  • Assign to sprints

  • Update custom fields

Rule Limits

  • Maximum 5 automation rules per agenda question

  • Each rule requires a unique webhook URL

  • Rules execute in parallel after meeting ends

Setup Process

Prerequisites

  • Jira project with automation permissions

  • NASA Scrum Master access to configure automation rules for a Stream

  • Understanding of Jira Automation basics

Step 1: Create Jira Automation Rule

  1. Navigate to Project Settings → Automation

  2. Click Create rule

  3. Select Incoming webhook as trigger

  4. Copy the webhook URL (save for Step 2)

  5. Configure your automation actions

jira-rule-builder-automation.webp
Automation for Jira

Step 2: Configure NASA Rule

  1. Open NASA Your Stream → Settings → Automation

  2. Click Add automation rule

  3. Enter:

    • Rule name (descriptive)

    • Select the Question (Agenda Item)

    • Select Item Type: (Text Item, Work Item)

    • Webhook URL (from Step 1)

    • Webhook Secret (from Step 1)

    • Notes (Optional)

  4. Click Create Rule

  5. Click Test to verify

    1. It will take the last available Team Journal as Testdata

edit automation rule.webp
Edit NASA Automation Rule

Step 3: Test Integration

  1. Update a test meeting stream

  2. Add items matching your rule conditions

  3. End the meeting

  4. Verify Jira automation executed

Payload Reference

NASA sends structured JSON payloads to your Jira webhook URLs when meetings end. Understanding these payload structures is essential for configuring your Jira Automation rules.

Text Item Payload

Used for creating new Jira issues from text items discussed during meetings:

  1. {
  2. "textItems": [
  3. {
  4. "summary": "textItem 1",
  5. "commentsConcat": "textItem 1"
  6. },
  7. {
  8. "summary": "textItem 2",
  9. "commentsConcat": "textItem 2"
  10. },
  11. {
  12. "summary": "textItem 3",
  13. "commentsConcat": "textItem 3"
  14. }
  15. ],
  16. "participant": "participantID"
  17. }

Field Descriptions:

  • textItems (array): Collection of text items from the meeting

    • summary (string): The title or main text of the item

    • commentsConcat (string): All comments from the discussion concatenated into a single string, separated by a new line between each

  • participant (string): Atlassian account ID of the meeting participant under whom the item appears

Use Cases:

  • Creating new Jira issues from meeting discussions

  • Auto-assigning created tasks to participants

Work Item (Issue) Payload

Used for updating existing Jira issues with meeting data:

  1. {
  2. "issues": [
  3. "P1-1",
  4. "P1-2"
  5. ],
  6. "data": {
  7. "participant": "participantID",
  8. "comments": {
  9. "P1-1": "Comment for P1-1",
  10. "P1-2": "Comment for P1-2"
  11. }
  12. }
  13. }

Field Descriptions:

  • issues (array): List of Jira issue keys to update

  • data (object): Additional meeting data

    • participant (string): Atlassian account ID of the meeting participant

    • comments (object): Map of issue keys to their corresponding meeting notes

      • Key: Issue key (e.g., "P1-1")

      • Value: Concatenated meeting notes/comments for that issue, separated by a new line between each other.

Use Cases:

  • Adding meeting notes as comments to existing issues

  • Reassigning issues based on the meeting participant

  • Bulk updating issue properties like Status

Note: The comments object uses issue keys as property names, allowing Jira Automation to access specific comments using {{webhookData.data.comments.get(issue.key)}} in smart values.

Using Smart Values

NASA provides these values in webhook payloads:

  • {{webhookData.participant}} - Meeting participant Atlassian account ID

  • {{webhookData.textItems}} - Array of text items with summary and commentsConcat fields

  • {{webhookData.issues}} - Array of Jira issue keys (e.g., ["PROJ-123", "PROJ-456"])

  • {{webhookData.data.comments}} - Map object containing issue keys to comment text

  • {{webhookData.data.participant}} - Participant ID (in issue item payloads)

Accessing nested values:

  1. {{webhookData.data.comments.get(issue.key)}} # Get comment for current issue
  2. {{currentTextItem.summary}} # Current text item title
  3. {{currentTextItem.commentsConcat}} # Current text item comments

Limitations

NASA Constraints

  • Maximum 5 rules per question

  • max 100 rules per Meeting Stream

  • No automatic Jira rule creation

Jira Automation Limits

  • Check your automation execution limits

  • Rate limits apply to webhook triggers

Troubleshooting

Webhook Not Receiving Data

  1. Verify webhook URL is exact (no extra spaces)

  2. Check Jira Automation rule is enabled

  3. Test with NASA's Test button

  4. Review Jira Automation audit log

Rules Not Triggering

  • Verify webhook URL is correct

  • Check Jira Automation rule is enabled

  • Ensure rule scope includes target project

Data Not Processing Correctly

  1. Check smart value syntax

  2. Test with simplified payload

Unexpected Assignments

  • Check for conflicting rules on same question

  • Verify rule conditions don't overlap

  • Review rule execution order in Jira

Best Practices

  1. Start Simple - Test basic rules before complex logic

  2. Use Descriptive Names - Include action and condition in rule names

  3. Test Rules First - Use the Test button to validate webhook connections

  4. Unique Names - Give each rule a descriptive, unique name

  5. One Action Per Rule - Keep rules simple and focused

  6. Check for Conflicts - Review existing rules before creating new ones

  7. Document Rules - Maintain a list of active automations

  8. Monitor Execution - Check Jira audit logs regularly

  9. Avoid Conflicts - Don't create overlaUse Case Examples

Practical automation recipes you can implement today: