Jelly-Tags

UpgradeManager Tag

This tag allow to perform, through the UpgradeManager, the upgrades described in dedicated XML file (same structured as JIRA Upgrade files). See [Kaamelot AddOn - UpgradeManager].

Usage is :

<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib">
	<UpgradeManager upgradeManagerClass="com.atlassian.jira.upgrade.MyUpgradeManager"/>
</JiraJelly>

Upgrade Tag

This tag may be used to execute a single Upgrade Task.

Usage is :

<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib">
	<Upgrade upgradeClass="com.atlassian.jira.upgrade.UpgradeTask"/>
</JiraJelly>

MigrateProject Tag

The tag MigrateProject provide a way perform a migration of a project.

Usage is :

  • Develop your migration Task (i.e. MyMigrateTask) extending com.atlassian.jira.migrate.MigrateTask.
  • Execute the Jelly Script :

    <JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib">
	<MigrateProject migrationClass="com.atlassian.jira.migrate.MyMigrateTask" projectKey="PRJ" issueKey="PRJ-10" />
</JiraJelly>

Import Tag

The tag Import allow to perform the execution of an ImportManager class (implementing com.atlassian.jira.import.IImportManager and even extending com.atlassian.jira.import.AImportManager) Usage is :

  • Develop your Import Manager (i.e. MyImportManager) overriding com.atlassian.jira.imports.AImportManager:

    protected abstract void importWorker(Reader _reader);
  • Execute the Jelly Script :

    <JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib">
</JiraJelly>

AddDetailedVersion Tag

This tag may be used to add detailled properties for JIRA Version entity ... Usage is : 
<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib">
	<AddDetailedVersion project-key="ABC" name="Ver 1" releaseDate="2007-12-31"/>
</JiraJelly>

TranslateConstant and TranslateConstants Tags

This tag may be used to add Constant Translation (Status, Resolution, Priorities, issueType, ...)...

Usage is :

<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib">
	<TranslateConstants id="" type="" locale="">
		<TranslateConstants name="" translatedName="" translatedDesc=""/>
		<TranslateConstants name="" translatedName="" translatedDesc=""/>
	</TranslateConstants>
	<TranslateConstants id="" name="" type="" locale="" translatedName="" translatedDesc=""/>
	<TranslateConstants id="" name="" type="" >
		<TranslateConstants locale="" translatedName="" translatedDesc=""/>
		<TranslateConstants locale="" translatedName="" translatedDesc=""/>
	</TranslateConstants>
</JiraJelly>

TransitionWorkflowExtended Tag

This tag may be used to perform Transition Workflow without or without Transition Screen (Fields).

Usage is :

<JiraJelly xmlns:addon="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib" xmlns:jira="jelly:com.atlassian.jira.jelly.JiraTagLib">
	<addon:TransitionWorkflowExtended user="user1" key="FOO-1" workflowAction="101" commment="A comment" commentLevel=""/>
	<addon:TransitionWorkflowExtended user="user1" key="FOO-1" workflowAction="102" commment="A comment" commentLevel="">
		<jira:AddCustomFieldValue id="customfield_10000" value="field value"/>
	</addon:TransitionWorkflowExtended>
</JiraJelly>

The TransitionWorkflowExtended Tag uses WorkflowTransitionUtilAddOnImpl as WorkflowTransitionUtil. It gives the ability, in case of Transition Screens, to assume existing value for a field, as submitted value.

For exemple, the Screen associated to a Transition requires to confirm the Assignee.

If you known that a user has been already assigned, you can let him as assignee by usgin the value --unchanged--. 

<JiraJelly xmlns:addon="jelly:com.atlassian.jira.jelly.JiraAddOnTagLib" xmlns:jira="jelly:com.atlassian.jira.jelly.JiraTagLib">
	<addon:TransitionWorkflowExtended user="user1" key="FOO-1" workflowAction="101" commment="A comment" commentLevel="" assignee="--unchanged--"/>
</JiraJelly>

Note that it can used for CustomFields.