Released Documentation
HomeSupport
  • Getting started
    • Overview
    • Concepts
    • Setup Guide
      • Installing Released
      • Embedding the Widget
      • Embedding the Page
      • Implementing User Verification
      • Changelog Description Field (optional)
  • Permissions
  • Global Settings
    • General
    • Design
    • Internal Domains
    • User Verification
  • Workspace
    • Overview
    • Dashboard
    • Changelog
      • AI Settings
      • Changelog filter
      • Creating and Managing Posts
      • Writing a Post
      • Publishing Updates
      • Templates
      • Editor
        • Images
        • Videos
        • Emojis
        • Keyboard Shortcuts
        • Categories
        • Versions
      • Filter
    • Roadmaps
    • Settings
      • General
      • Access
      • Portal
        • Page Embed
        • Widget Embed
      • Publishing
        • Confluence
        • Email
        • Jira issue links
    • Integrations
      • Framer
      • Webflow
      • Slack
      • Aura
      • Cosmos
      • Karma
      • Scroll Viewport for Confluence
  • Resources
    • AI Tips
      • Create Output in Other Languages
      • Include a Documentation Link in the Output
      • Creating Structured Output
    • Troubleshooting
      • Permissions Issues
    • How-Tos
      • Accessing Custom Fields
      • Configuring Dark Mode
      • Finding the Channel ID
      • Ensuring JavaScript Resource Stability for PCI Compliance
      • How to Open the developer console to check for errors
      • How to Apply Atlassian Marketplace App Promo Codes for Cloud
      • Configuring Content Security Policies (CSP) for Released Embeds
Powered by GitBook
On this page
  • Overview
  • How to
  • 1. Setting up the automation
  • 2. Reference the data in your AI prompt

Was this helpful?

  1. Resources
  2. How-Tos

Accessing Custom Fields

PreviousHow-TosNextConfiguring Dark Mode

Last updated 3 months ago

Was this helpful?

Overview

Released lets you choose which description field to use for generating release notes. But every so often, you might want to include information from other fields in your release notes as well.

Common examples are:

  • Documentation links

  • Product area

  • Theme

  • Customer

This guide outlines a simple workaround to include additional fields in your release notes until native support is available.

Here’s how it works:

  1. Copy field values into the description field using automation.

  2. Adjust your AI prompt to reference those fields.

How to

With Jira Automation, you can easily copy values from other fields into the description field used for generating release notes.

You can trigger this automation manually or automatically when an issue’s status changes.

Follow the step-by-step guide below to set it up.

1. Setting up the automation

Adding a trigger

First, decide how you want to trigger the automation. The most common options are:

  • Manual trigger (shown above) – Run the automation on demand.

  • Workflow transition trigger – Automatically trigger the automation when an issue’s status changes.

Adding an action

Once the automation is triggered, the next step is to define an action. In this case, we want to edit the description field used to create the release notes.

In the below example, we’re updating the description field by:

  1. Keeping the original description at the top to preserve existing information.

  2. Adding a section labeled “Other Information” below, where we include values from various issue fields.

  3. Structuring the field data as key value pairs. This will allow for referencing the fields in the AI prompt.

Click on the curly brackets in the bottom right of the text editor to easily access the available fields for the issues.

Example

{{issue.description}}

h3. Other information

Assignee: {{assignee.displayName}}
Versions: {{issue.fixVersions.name}}
Documentation: {{issue.customfield_10414}} // the custom field ID will differ.

2. Reference the data in your AI prompt

Once the data is available in the description field, you can reference it directly in the AI prompt. Simply use the field name as specified in the structured format above to ensure consistent output.

For more detail on how to write an AI prompt using custom fields read Creating Structured Output

If you are not familar with Jira automations, we recommend that you read the first.

Getting Started Guide for Jira Automations