JIRA Capture (previously Bonfire) is now called Capture for JIRA. Learn more.

Skip to end of metadata
Go to start of metadata

Templates enables you to capture issues even faster during testing, by automatically populating fields in issues with your predefined values. Templates are remembered on your JIRA server, so your templates remain the same regardless of which browser you are testing in. Templates are also shared, so you can create one template that your whole team can use.

Creating and using templates

To create a new template, go to the "Templates" tab in the Capture for JIRA browser extension, then click "Add Template" under the "Mine" section. Here, you can pre-fill an issue creation form with any information you would like. (e.g. a particular project, version, or component you are working). Selecting the option "Attach Screenshot by Default" will include a screenshot attachment automatically when you are applying a template.

You can have as many templates as you like, so you can have very specific templates for issues that you may wish to raise during testing.

Templates are used when creating an issue. To do this, simply choose one from the "Use Template" menu on the Create Issue tab in the Capture for JIRA browser extension. The "Use Template" menu will only show templates that you have marked as "Favorite" with a star ((star)). By default, all templates you create are marked favorite for you.

Using a template will keep it selected until you choose otherwise – even across multiple uses of the browser extension.

A template can also be assigned as the default template for a shared test session, allowing all participants of the test session to create consistent issues. For more information on creating test sessions, please read Working with Sessions.

Using variables in a template

Variables allow templates to contain dynamic information, and are only evaluated into actual values when the template is used during issue creation. Variables previously only worked when used in a template, but as of JIRA Capture 2.2 (now Capture for JIRA), they can be used at any time during the issue creation process.

To use a variable, enter the variable name surrounded by braces ("{" and "}") into a text field on the template or issue creation forms.

By default, Capture for JIRA ships with four variables:

  • {cookies} - Are cookies turned on? Value is either true or false.
  • {useragent} - Browser information
  • {title} - Current page title
  • {url} - Current page URL

Creating your own variables to use

The default variables shipped with Capture for JIRA are only a start – you can also create your own variables to do different things. To create another variable, simply click "Add Variable" in the Templates tab of the browser extension. For each variable, you need to provide 2 pieces of information:

  • the name - this is the variable name. You use the variable in templates by enclosing the variable name in '{' and '}'
  • the javascript selector - this is the javascript that will evaluate when you run the variable. This happens when you select a template to use in the create issue tab.

Some other examples:


Javascript Selector



This is one specific to JIRA itself. In our JIRA footer, we always include the JIRA version and build numbers. This javascript selector will get this information for us

new Date().toDateString()

Today's date.


Chrome & Safari






Will insert any text that's already selected.

Note that the javascript for this differs across browsers, so you will need to create separate variables for each browser you wish to use this in.

Sharing templates and variables

Once you have templates working the way you want, you can also opt to share it with your team by marking the "Share this template" checkbox.

Your teammates will now be able to see this template in their list of available templates to use.

If they "favorite" the template, it will be made available for use in their issue creation under the "Use Template" menu. Note - using a shared template will also include any variables which are included in the template.

Control field visibility using templates

The checkboxes on the template form control the visibility of the field when the template is used. This means that you can choose to view only the fields that matter to you when using the template. These hidden fields will also apply for anyone using your shared template. Mandatory fields that are required for issue creation will always be visible, to minimize the chance of issue creation errors.


  • No labels


  1. We're evaluating JIRA Capture and I'm noticing that, when creating a template, some fields I've not specified to be showing within the template are showing anyway ... not all ... but some. This has nothing to do with changing a project or issue type after selecting a template or required fields (they're not). What am I missing?

  2. There needs to be a way to hide required fields if default values are set.

    For example, you may not want customer to be selecting the type if the issue. Customer submits the request, development team determines if it is a bug, issue or new feature. The fewer fields customer need to fill in, the better.

  3. Custom JavaScript is not working.

    In our application there is the version available as app.version.

    However, trying to use this as vaiable in JIRA Capture results in "TypeError: Cannot read property 'version' of undefined".

    How can this be accomplished?


  4. This has got to be a stupid question, but how do you delete a template? I can't find anything in Capture nor in the JIRA console to manage/delete them.

  5. Hi,

    Can anyone tell me if you are able to add a JIRA search field to a template that will search JIRA for any potential duplicate bugs or requirements, thereby preventing the tester from creating duplicate bug or requirement tickets? If you can do this, how is it done? Thanks

  6. @rick crow i'm seeing the same issue.  fields i've deselected still appear for me and my team when using the tempate (sad)

  7. Confluence is a wiki. You can use it to collaborate on writing and sharing content with your team. Your team can be as small or as big as you like. It could encompass the whole world. Your content can be as simple or as rich as you like. It can be just words, or you can add images, diagrams, activity streams, web service integration and more.

    In a nutshell, a wiki is a piece of software that runs on a server. It publishes web pages that you can read via a web browser such as Mozilla Firefox, Google Chrome or Microsoft Internet Explorer. The thing that makes wiki pages different from other web pages is the edit button. Provided that you have the right permissions, you can edit the page, save your changes, and the updates will be visible to other people immediately!!!

  8. I'm having trouble getting the "Epic Link" to show up in other projects. One project shows the epic Link, but when I switch over to another project,  the epic link tab is no longer shown. (Trying to scan through anything to help solve this issue.)

  9. Are custom Javascript variable still not working?  I see that Peter Gasser asked this question three years ago.  Is this still not resolved?  Without access to your custom JS variables, my organization will not be able to use this otherwise very useful plugin.

    1. If I remember correctly, this is a limitation of e.g. the security context of Chrome.

      What you can do however is write stuff you need to have available into a hidden DOM element, and declare a variable in JIRA capture which uses some sort of:

      document.getElementById('your_id_here').value / innerHTML / ...
      1. That will work, I guess.

        Thanks, Peter Gasser