Jump to a Section

Overview

Authorization of JIRA Software

Before connecting JIRA Software to Azuqua, please ask your JIRA administrator to ensure that the “Accept Remote API calls” option has been turned on in the system admin screen.

  1. Enter in an Account Nickname. This should be unique so you can authorize multiple JIRA accounts and tell them apart.
  2. Your JIRA Username and Password.
  3. Enter your Instance URL. i.e. “yourcompany.atlassian.net”. Do not include the “https//:”
  4. Click “Create” to save your configuration.

NOTE: If you change your JIRA password, you will need to update all of your connections to use the new password. For help doing that, see View and Manage Connections. JIRA automatically locks you out of the API if 4 calls are made with old or incorrect passwords. If any active FLOs attempt to use your old password, all calls will fail (even those that use the correct credentials) and you will have to change your password to regain API access.

    Events

    • Issue Deleted

      Triggers a FLO when an issue is deleted in JIRA.

      Options

      • Project (drop down menu): The project you wish to surveil for deleted issues.
      • JQL Query (text): Add a JQL query to dictate which issues will trigger the FLO. JQL?

      Output Fields

      • Webhook
        • Raw Data (object): The raw webhook data for the issue.
      • Issue
        • Issue ID (text): The ID of the issue.
        • Self (text): The URL to the issue.
      • context
        • Execution ID (text): The unique identifier for the execution of the FLO.

      Additionally, all data present on an issue page can be outputted.

    • Issue Transitioned

      Triggers a FLO when an issue’s status is changed in JIRA.

      Options

      • Project (drop down menu): The project you wish to trigger the FLO when an issue is transitioned within it. Or choose “–All Projects–”.
      • JQL Query (text): Add a JQL query to dictate which issues will trigger the FLO. JQL?

      Output Fields

      • Webhook
        • Raw Data (object): The raw webhook data for the issue.
      • Issue
        • Issue ID (text): The ID of the issue.
        • Self (text): The URL to the issue.
      • Transition
        • Transition ID (number): The ID for the transition.
        • From (text): The original status.
        • To (text): The new status.
      • User
        • Name (text): The username of the user who made the transition.
        • Display Name (text): The display name of the user who made the transition.
        • Active (T/F): If the user is active or not.
        • Email (text): The email of the user who made the transition.
      • context
        • Execution ID (text): The unique identifier of the execution of the FLO.

      Additionally, all data present on an issue page can be outputted.

    • Issue Updated

      Triggers a FLO when an issue is updated in JIRA.

      Options

      • Project (drop down menu): The project you wish to surveil for new issues.
      • JQL Query (text): Add a JQL query to dictate which issues will trigger the FLO. JQL?

      Output Fields

      • Webhook
        • Raw Data (object): The raw webhook data for the issue.
      • Issue
        • Issue ID (text): The ID of the issue.
        • Self (text): The URL to the issue.
      • context
        • Execution ID (text): The unique identifier for the execution of the FLO.

      Additionally, all data present on an issue page can be outputted.

    • Issue Updated - Polling

      Triggers a FLO when an issue is updated in JIRA (polling method).

      Options

      • Project (drop down menu): The project you wish to surveil for updated issues.

      Output Fields

      You can choose which outputs you want by clicking the settings button at the bottom right corner of the card. Below are example outputs:

      • Issue
        • Issue ID (text): The ID of the issue.
        • Self (text): The URL to the issue.
        • Key (text): The Issue Key.
      • context
        • Execution ID (text): The unique identifier for the execution of the FLO.

      Additionally, all data present on an issue page can be outputted.

    • New Comment

      Triggers a FLO when a new comment is created in JIRA.

      Options

      • Project (drop down menu): The project you wish to trigger the FLO when a comment is added within it.

      Output Fields

      • Webhook
        • Raw Data (object): The raw webhook data for the comment.
      • Issue
        • Issue ID (text): The ID of the issue.
      • Comment
        • Comment ID (text): The ID of the comment.
        • URL (text): The URL to the comment.
        • Body (text): The content of the comment.
        • Created Date (date and time): When the comment was posted.
      • Author
        • Name (text): The username of the author of the comment.
        • Display Name (text): The display name of the author of the comment.
        • Active (T/F): If the user is active or not.
      • context

        • Execution ID (text):The unique identifier of the execution of the FLO.

        Additionally, all data present on an issue page can be outputted.

    • New Issue

      Triggers a FLO when a new issue is created in JIRA.

      Options

      • Project (drop down menu): The project you wish to surveil for new issues.
      • JQL Query (text): Add a JQL query to dictate which issues will trigger the FLO. JQL?

      Output Fields

      • Webhook
        • Raw Data (object): The raw webhook data for the issue.
      • Issue
        • Issue ID (text): The ID of the issue.
        • Self (text): The URL to the issue.
      • context
        • Execution ID (text): The unique identifier for the execution of the FLO.
    • New Issue - Polling

      Triggers a FLO when a new issue is created in JIRA (polling method).

      Options

      • Project (drop down menu): The project you wish to surveil for new issues.

      Output Fields

      You can choose which outputs you want by clicking the settings button at the bottom right corner of the card. Below are example outputs:

      • Issue
        • Issue ID (text): The ID of the issue.
        • Self (text): The URL to the issue.
        • Key (text): The Issue Key.
      • context
        • Execution ID (text): The unique identifier for the execution of the FLO.

      Additionally, all data present on an issue page can be outputted.

    • New Project

      Triggers a FLO when a project is created in JIRA.

      Output Fields

      • Webhook
        • Raw Data (text): The raw webhook data with the project information.
      • Project
        • Key (text): The project key, an identifier, which is generally short i.e. “CP”.
        • Project ID (number): The ID for the project i.e. “10923”.
        • Lead Username (text): The username of the project lead.
        • Name (text): The name of the project.
        • API Resource URL (text): The API Resource for the project.
        • URL (text): The URL for the project.
      • Context
        • Execution ID (text): The ID for the execution of the FLO.
    • New Work Log Entry

      Triggers a FLO when a new work log entry is made in JIRA.

      Options

      • JQL Query (text): An optional query to dictate which work logs trigger the FLO. JQL

      Output Fields

      • Webhook
        • Raw Data (object): The raw webhook data for the work log.
      • Entry
        • URL (text): The URL for the work log entry.
        • Comment (text): The comment on the work log.
        • Started At (date and time): When the work was started.
        • Time Spent (text): The time spent working.
        • Time Spent (seconds) (number): The time spent, in seconds, working.
        • Worklog ID (number): The ID for the work log.
        • Parent Issue ID (number): The ID of the issue the work is on.
      • Visibility
        • Type (text): The type of visibility.
        • Level (text): The level of visibility.
      • Author
        • Name (text): The username of the author.
        • Display Name (text): The display name of the author.
        • Active (T/F): If the author is active or not.
      • Context
        • Execution ID (text): The unique identifier for the execution of the FLO.
    • Project Updated

      Triggers a FLO when a project is updated in JIRA.

      Output Fields

      • Webhook
        • Raw Data (text): The raw webhook data with the project information.
      • Project
        • Key (text): The project key, an identifier, which is generally short i.e. “CP”.
        • Project ID (number): The ID for the project i.e. “10923”.
        • Lead Username (text): The username of the project lead.
        • Name (text): The name of the project.
        • API Resource URL (text): The API Resource for the project.
        • URL (text): The URL for the project.
      • Context
        • Execution ID (text): The ID for the execution of the FLO.

    Actions

    • Add Issue to Sprint

      Adds an existing issue to a Sprint in JIRA.

      Input Fields

      • Sprint
        • Sprint ID (text): The ID of the sprint you want to add to.
      • Issues
        • Issue IDs or Keys (list of text): Either the ID or the Key of the issues you wish to add to the sprint. The key can be found in the URL of the Issue (https://yourdomain.atlassian.net/projects/HT/issues/**HT-22** where HT is the Project Key). You can find the Issue ID by using the Key to search in ‘Read Issue’. They are also both given when an issue is created in the designer by using ‘Create Issue’.

      Output Fields

      • There are no output fields for this card.
    • Build Issue Object

      Build an issue object for use with "Create Issues"

    • Create Comment

      Creates a comment on an issue in JIRA.

      Input Fields

      • Issue
        • ID or Key (text): The ID or the key for the issue you wish to comment on. The key can be found in the URL of the issue and is the Project key and the numbers attached to it i.e. “CP-49”. The Issue ID and Key can also be found by using the ‘Search Issues’ action card.
      • Comment
        • Body (text): The content of the comment.

      Output Field

      • Response
        • Status Code (number): The code for the status of the attempt (if the comment post was successful). Status codes are defined here.
    • Create Issue

      Creates a new issue in Jira.

      Options

      Choose “–All Projects–” or “–All Issue Types–” if you want to be able to run different types each time the FLO is executed.

      • Project (drop down menu): A list of existing projects in your JIRA account. You can also select “–All Projects–” if you want to enter the project name as an input.
      • Issue Type (drop down menu): The type of issue you will be creating. You can also choose “–All Issue Types–” if you wish to use the issue type as an input.

      Input Fields

      Input fields are dynamically generated based on your Options selections.

      • Project (if “–All Projects–” is selected)
      • Fields
        • Issue Type _(text): (_If “–All Issue Types–” is chosen) The type of issue.
        • Summary (text): A summary of the issue.
        • Component/s (list of text): Enter in the component i.e. “10000”. Components are sub-sections of a project. They are used to group issues within a project into smaller parts. You can set a default assignee for a component. This will override the project’s default assignee, for issues in that component.
        • Description (text): A description of the issue. You can also mention a user in the description to send them an email notification by using the “@” and then their JIRA username.

      Output Fields

      • Issue
        • Key (text): The issue key; an identifier.
        • Issue ID (text): The ID of the issue.
        • URL (text): The URL to the issue.
        • API Resource URL (text): The URL directing to the API resource.
    • Create Issues

      Create multiples issues at once

    • Create Project

      Creates a project in JIRA.

      Input Fields

      • Project
        • Name (text): The name for the project. i.e. “Example Project”.
        • Key (text): The key; should be short identifier for the project i.e. “EP”.
        • Description (text): A description of the project.
        • Lead Username (text): The username of the lead for the project.

      Output Fields

      • Project ID (text): The ID of the project.
      • Key (text): The project key-an identifier- created above.
      • URL (text): The URL for the project.
      • API Resource URL (text): The API Resource URL for the project.
    • Create Sprint

      Creates a sprint in a board in JIRA.

      Options

      • Board (drop down menu): Choose from existing boards.

      Input Fields

      • Sprint
        • Name (text): The name of the sprint.
        • Start Date (text): The start date. YYYY-MM-DDTHH:MM:SS.MMMZ i.e. “2017-07-21T22:33:58.411Z”.
        • End Date (text): The end date. YYYY-MM-DDTHH:MM:SS.MMMZ i.e. “2017-07-21T22:33:58.411Z”.
        • Goal (text): A goal for the sprint.

      Output Field

      • Sprint ID (number): The ID for the sprint created.
    • Delete Issue

      Deletes an issue in JIRA.

      Input Field

      • Issue
        • ID or Key (text): The ID or Key of the Issue you wish to delete. The Issue Key can be found in the URL of the issue (https://your domain.atlassian.net/projects/HT/issues/HT-123) or by using ‘Search Issues’.

      Output Fields

      • Response
        • Status Code (number): The code for the status of the attempt (if the deletion was successful). Status codes are defined here.
    • Delete Project

      Deletes a project in JIRA.

      Input Field

      Output Field

      • Response
        • Status Code (number): The code for the status of the attempt (if the deletion was successful). Status codes are defined here.
    • Delete Sprint

      Deletes a sprint in JIRA. Note: Only future sprints can be deleted.

      Input Field

      • Delete By
        • Sprint ID (number): The ID of the sprint you wish to delete.

      Output Fields

      • There are no output fields for this card.
    • Download Attachment

      Downloads a file from JIRA.

      Input Field

      • Attachment
        • Attachment ID (text): The ID of the attachment to be downloaded.

      Output Field

      • Attachment
        • File Content (file): The attachment.
    • Dynamic Auth Custom API Action

      Make a custom API request to the JIRA API with dynamic authentication

    • Edit Sprint

      Updates the details of a sprint in JIRA.

      Input Fields

      • Update By
        • Sprint ID (number): The ID of the sprint you want to update.
      • Sprint
        • Name (text): The name of the sprint.
        • State (drop down menu): Change the state to closed or active.
        • Start Date (text): The date the sprint starts. YYYY-MM-DDTHH:MM:SS
        • End Date(text): The date the sprint ends. YYYY-MM-DDTHH:MM:SS
        • Goal (text): The goal of the sprint.
    • HTTP Request

      Make an authenticated HTTP request to the JIRA API

    • List Issues

      Lists all issues in a project in JIRA.

      Options

      • Project (drop down menu): Choose the project you wish to use, or use “–All Projects–” or “–Insert ID–” to have the project name or ID as an input value.
      • Issue Type (drop down menu): Choose the issue you wish to use, or use “–All Issue Types–” or “–Insert ID–” to have the issue type or ID as an input value.

      Input Fields

      • Options
        • Issue Type ID or Name (text): If ”–All Issue Types–” or “–Insert ID–” is chosen. The type ID or Name of the Type of issue.
        • Project Name or ID (text):If ”–All Projects–” or “–Insert ID–” is chosen. The name or ID of the project you wish to list the issues from.
        • Limit (number): The maximum number of issues the card should return.
        • Offset (number): If you wish to have an offset in what is returned, the number of issues that will be ‘skipped’ before returning the list of issues.

      Output Fields

      • Result
        • Issues (list of objects): Returns a list of the issues found in that project and their information. These are dynamically generated based on the issue.
    • List Projects

      Lists all projects and their information in JIRA.

      Input Fields

      There are no input fields for this card.

      Output Fields

      • Result
        • Projects (list of objects):
          • Key (text): The Project key; an identifier.
          • Project ID (text): The project ID.
          • Description (text): A description of the project.
          • API Resource URL (text): A URL to the API resource for the project
          • URL (text): The project’s URL.
          • Category (text): The category given to the project.
          • Issue Types (list of text): A list of the issue types.
          • Lead Username (text): The username of the lead of the project.
          • Lead Display Name (text): The display name of the lead of the project.
          • Lead Active (T/F): If the lead is active or not.
    • List Work Logs

      Lists all work logs for an issue in JIRA.

      Input Fields

      Output Field

      • Result
        • Work Logs (list of objects): A dynamically generated list of all existing work logs and their information.
    • Log Work

      Logs work on an issue in JIRA. Note: If you need to edit the visibility via Azuqua, you will need to use the JIRA HTTP Request card and have System Admin credentials.

      Input Fields

      • Issue
      • Worklog
        • Comment (text): A comment regarding the work.
        • Time Started (text): The date/time the work began. The date/time can be formatted using ISO UTC (e.g. “2016-09-07T16:55:25.670Z”) or offset notation (e.g. “2016-09-07T16:55:25+00:00”) or Jira’s expected format (e.g. “2017-06-16T02:48:07.240+0000”).
        • Time Spent (seconds) (number): The amount of time, in seconds, spent on the issue i.e. “3600” for an hour of work.

      Output Field

      • Response
        • Status Code (number): The code for the status of the attempt (if the update was successful). Status codes are defined here.
    • Read Issue

      Reads an issue in JIRA.

      Options

      • Project (drop down menu): The project the issue is located in. Or choose “–All Projects–” if you wish to have the project name be an input.
      • Issue Type (drop down menu): The type of issue to be read. Or choose “–All Issue Types–” if you wish to have the issue type as an input.

      Input Field

      • Issue
        • ID or Key (text): The ID or Key of the Issue you wish to read. The Issue Key can be found in the URL of the issue (https://your domain.atlassian.net/projects/HT/issues/HT-123) or by using ‘Search Issues’.

      Output Fields

      • Issue
        • Issue ID (text): The ID of the issue i.e. “12388”.
        • Self (text): The URL to the issue.
        • Key (text): The Issue’s key i.e. “HT-123”.
    • Read Project

      Reads a project in JIRA.

      Input Field

      Output Fields

      • Project
        • Key (text): The project key; an identifier.  i.e. “TB”.
        • Project ID (number): The ID of the project. i.e. “10110”.
        • Name(text): The name of the project i.e. “Test Project”.
        • Type(text): The type of project i.e. “software”.
        • URL(text): The URL linking to the project.
        • API Resource URL(text): The API Resource URL for the project.
        • Description(text): The description provided for the project.
        • Assignee Type(text): Types of assignees found here.
        • Issue Types(list of text): A list of the issues.
      • Project Lead
        • Username (text): The username of the lead of the project.
        • Display Name (text): The display name of the lead of the project.
        • Active (T/F): If the project is active or not.
    • Read Sprint

      Uses a the Sprint ID to read a sprint in JIRA.

      Input Fields

      • Read By
        • Sprint ID (number): The ID of the sprint you want to read. i.e. “85”.

      Output Fields

      • Sprint
        • Name (text): The name of the sprint.
        • State (text): closed or future.
        • Start Date (date): The start of the sprint.
        • End Date (date): The end of the sprint.
        • Complete Date (date): The date the sprint was completed (if at all).
        • Board ID (number): The ID of the board the sprint is on.
        • Goal (text): The sprint goal.
    • Read Sprint Issues

      Returns a list of issues within a sprint in JIRA.

      Input Fields

      • Read By
        • Sprint ID (number): The ID of the sprint.
        • Start At (number): The offset of the data returned.
        • Max Results (number): The maximum number of issues the card should return.
        • JQL Query (text): A JIRA Query Language query if you wish to query the search. ?

      Output Fields

      • Result
        • Issues (list of objects): A dynamically generated list of issues in the sprint and their information.
    • Read User

      Reads a user in JIRA.

      Input Field

      • User
        • Key (text): The unique identifier of the user, usually the username.

      Output Fields

      • User
        • Display Name (text): The display name of the user.
        • Username (text): The username of the user.
        • Email Address (text): The user’s email address.
        • Active? (T/F): If the user is active or not.
    • Search Issues

      Searches for an issue in JIRA.

      Options

      • Project (drop down menu): The project that contains the issue you’re searching for. You can also choose “–All Projects–” to add the project name as an input.
      • Issue Type (drop down menu): The type of issue you will be searching for. Or choose “–All Issue Types–” to have the Issue type as an input.
      • Result Set (drop down menu): If you want the card to return all matches, or just the first match that is found.

      Input Fields

      • Options
        • Offset (number): An offset for the results. i.e. if the card finds 50 issues and you want to return the last 20, your offset would be 30 and max result would be 20.
        • Max Results (number): The maximum number of results the card will return.
      • Search By
        • Assignee (text): The assignee of the issue.
        • Category (text): The category given to the issue.
        • Comment (text): A comment on the issue.
        • Created (text): When the issue was created.
        • Creator (text): The username of the user who created the issue.
        • Description (text): A description of the issue.
        • Due Date (text): When the issue is due.
        • Last Viewed (text): The last time the issue was viewed.

      Output Fields

      If “All Issues” is chosen in the Options, the output will be a list of issues and their information.

      • Issue
        • Key (text): The key of the issue i.e. “TP-123”.
        • Issue ID (text): The ID of the issue i.e. “12655”.
        • API Resource URL (text): The URL of the api resource for the issue.
        • URL (text): The URL of the Issue.
    • Search Issues by JQL

      Uses a JIRA Query language (JQL) query to get a list of issues in JIRA.

      Options

      • Enviroment : Choose the enviroment where your Jira instance is hosted is hosted. Its either On-Premise or Cloud.

      Input Fields

      • Search By
        • JQL Query (text): A JQL query to dictate the issues returned. JQL?
        • Limit (number): The maximum number of issues returned.
        • Offset _(_number): An offset for the list of issues returned.

      Output Fields

      • Result
        • Issues (lists of objects): A list of the issues and their information.
          • Key (text): The Issue’s key.
          • Issue ID (number): The Issue ID of the issue.
          • URL (text): The URL of the issue
          • API Resource URL (text): The URL to the API resource for the issue.
    • Search Projects

      Searches for a project in JIRA.

      Options

      • Result Set (drop down menu): If you want the card to return all matches, or just the first match that is found.

      Input Fields

      • Project
        • Name (text): The name of the project.
        • Category (text): The project category.
        • Lead Username (text): The username of the lead.
        • Lead Display Name (text): The display name of the lead.

      Output Fields

      If “All Projects” is chosen in the Options, the output will be a list of projects and their information.

      • Project
        • Name(text): The name of the project i.e. “Test Project”.
        • Key (text): The key of the project i.e. “TP”.
        • Project ID (text): The ID of the project i.e. “10010”.
    • Search Projects by Issue

      Uses an issue ID or key to find a project in JIRA.

      Input Field

      Output Fields

      • Project
        • Project ID (text): The ID of the project found.
        • Key(text)**: The project’s key.
        • URL(text)**: The URL for the project.
        • API Resource URL (text): The API Resource for the project.
    • Search Users

      Searches for a user’s username in JIRA.

      Options

      • Result Set (drop down menu): If you wish to return all matches or just the first match to your search query.

      Input Field

      • User
        • Query (text): Enter a name, username, or email address to search with. i.e. “sarah” or “sarah@companyname.com”.

      Output Field

      Will return either a single username or a list of usernames depending on the ‘Result Set’ selection in the options.

      • Username (text): The username of the matched user.
    • Transition Issue

      Changes the status of an issue in JIRA.

      Input Fields

      • Transition
        • Issue ID or Key (text): The ID or key of the issue you wish to transition.
        • Transition To (text): The new status of the issue. Either “In Progress”, “To Do”, or “Done”.
        • Comment (text): Add a comment.

      Output Fields

      • Response
        • Status Code (number): The code for the status of the attempt (if the transition was successful). Status codes are defined here.
    • Update Issue

      Updates an issue in JIRA.

      Options

      • Project (drop down menu): Choose the project you wish to use, or use “–All Projects–” or “–Insert ID–” to have the project name or ID as an input value.
      • Issue Type (drop down menu): Choose the issue you wish to use, or use “–All Issue Types–” or “–Insert ID–” to have the issue type or ID as an input value.

      Input Fields

      Input fields are dynamically generated based on your option selections. If you do not provide the project name or the issue type as an option, you will need to input them here.

      • Issue
      • Fields fields are dynamically generated based on the issue type.
        • Summary (text): A summary of the issue.
        • Components (list of text): Add components to the issue.

      Output Field

      • Response
        • Status Code (number): The code for the status of the attempt (if the deletion was successful). Status codes are defined here.
    • Update Project

      Updates a project in JIRA.

      Input Fields

      • Project
        • ID or Key (text): The ID or the key of the project you want to edit. You can use ‘Search Projects’ or ‘Search Projects by Issue’ to find this information, if you don’t already have it in the FLO.
      • Fields
        • Key (text): A new key for the project.
        • Name (text): The name of the project.
        • Description (text): A description of the project.
        • Lead Username (text): The username of the lead of the project.

      Output Field

      • Response
        • Status Code (number): The code for the status of the attempt (if the update was successful). Status codes are defined here.
    • Upload Attachment

      Attaches a file to an issue in JIRA.

      Input Fields

      • Issue
      • Attachment
        • File Content (file): The file that will be uploaded.

      Output Field

      • Attachment
        • Attachment ID (text): The ID of the attachment.
    • Create Version

      Creates a Version in JIRA.

      Input Fields

      • Version
        • Name (text): The unique name of the version.
        • Release Date (text): The release date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).
        • Start Date (text): The start date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).
        • Project ID (number): The ID of the project to which this version is attached. Required when creating a version.
        • Description (text): The description of the version.
        • Archived (T/F): Indicates that the version is archived.

      Output Field

      • Response (string): The response from Jira API.
        • Status Code (number): Status of the response from Jira API.
        • Self (text): A link to the Version.
        • ID (text): The ID of the Version.
        • Description (text): The description of the version.
        • Name (text): The unique name of the version.
        • Archived (T/F): Indicates that the version is archived.
        • Released (T/F): Indicates that the version is released.
        • Project ID (number): The ID of the project to which this version is attached.
    • Update Version

      Updates a Version in JIRA.

      Input Fields

      • Version
        • ID (text): The ID of the Version being modified.
        • Name (text): The unique name of the version.
        • Release Date (text): The release date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).
        • Start Date (text): The start date of the version. Expressed in ISO 8601 format (yyyy-mm-dd).
        • Description (text): The description of the version.
        • Archived (T/F): Indicates that the version is archived.
        • Released (T/F): Indicates that the version is released.
        • Move Unfixed Issues To (text): The URL of the self link to the version to which all unfixed issues are moved when a version is released.

      Output Field

      • Response (object): Values returned from the Jira API.
        • Status Code (text): Status of the response from Jira API.
        • Self (text): A link to the Version.
        • ID (number): The ID of the Version.
        • Description (text): The description of the version.
        • Name (text): The unique name of the version.
        • Archived (T/F): Indicates that the version is archived.
        • Released (T/F): Indicates that the version is released.
        • Project ID (text): The ID of the project to which this version is attached.