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
  • Issue description
  • Prompt
  • Preview

Was this helpful?

  1. Resources
  2. AI Tips

Include a Documentation Link in the Output

Overview

Adding links to in depth articles or documentation is a great way to keep the product update short while giving readers the opportunity to dive into the details.

Using a custom prompts, you can easily incorporate links to other resources and create a consistent structure for your output.

How to

Issue description

Let's assume we have a ticket with the following description:

## Overview
It would be great if changes to a task would be recorded. 

Information that would be useful to know is: 

* Assignee
* Due date
* Status changes

## Documentation
https://docs.released.so

We want to generate a description from the overview section and add the documentation link to the bottom of the description with a pre-fix of "Learn more:"

Prompt

Switch the Base prompt setting from Default to Custom.

In your custom prompt, keep the first part as is.

Then, add additional instructions to format the description, followed by an example:

Remove details not relevant for a release announcement such as mentions of a workaround or steps to reproduce. Remove internal language, like use-cases and requirements. Describe bugs and problems as resolved. 

Use the following structure for the description. Consider text in angular brackets as placeholders. Output in HTML format:
START
[Title]
[Description]

Learn more: [Documentation url]
END

That's it.

Preview

Preview the prompt in the Issue specific prompts section.

  • Pick an issue type

  • Select an issue in the top right of the issue type box

Once an issue has been selected, the preview, using the above prompt, will start to load.

The above prompt will apply to all issue types. If you would like to only apply the instructions to certain issue types, simply move the prompt into the custom prompt setting for the specific issue types.

PreviousCreate Output in Other LanguagesNextCreating Structured Output

Last updated 3 months ago

Was this helpful?

Prompt Preview