Table of contents
Git tags identify specific release versions of your code in a particular branch and do not change when the branch moves on. A tag is an alias for a commit hash, much like symbolic names for a given revision. It is typically used to mark a particular point in the commit. It is like a branch with a read-only attribute. The git tags are accessible in the developer panel.
The git tags refers to merged, released work.v2.8.0+
The Git Integration for Jira app supports both lightweight and annotated tags. The tags are loaded separately from the rest of the Git Source Code.
Tags cannot be moved since it is linked to a specific commit and are not pushed by default.
The Git for Jira app supports two types of git tags:
- lightweight – shows only the commit object
- annotated – shows the message, author and the tag object followed by the commit
A lightweight tag can be use for marking a version or some specific commits that you will need to use later on — like a temporary object label. It does not contain extra information.
Annotated tags can contain a message, author and date different than the commit that they are pointing to — like describing a release without making a release commit.
The git tag is displayed on the right sidebar if it is enabled in the General Settings of the Git Integration app > Calculate and show Git tags in Git Source Code panel.
This feature is disabled by default for existing installations and is automatically enabled for new installations of Git Integration app.
The Git Integration for Jira app will show the last 3 and first tags if no filter is set. If the filter is set, the Git for Jira app will use it and will display the tags sorted in ascending order by date.
If there are several git tags listed, click the more... label link to expand the list in increments of five tags.
Move the mouse pointer over the tag to display the following tooltip information:
- Repository Name
- Date / Time
- Commit author name and email address (if available)
- Message (if any)
Tags are only associated with the Jira issue by Jira keys that are specified in commits that belong to the tag. Specifying a Jira key in the name of a tag does not associate this tag with the mentioned ticket.