Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Notice that a mapping enables  issue creation and linking via the quick action button only if the Quick Action Button box is checked.

Precondition:

  • configure a partnership as per the example below

...

1

Go to an issue belonging to the project selected as Source Project and having as Issue Type the Source Issue Type.

Issue view screen

2

The Herzum Quick actions panel shows the button associate to the configured mapping.

 

Herzum Quick actions panel

3

Click the Herzum Quick Action button to display the Create Screen of the issue to be created on the Target Project and having the Target Issue Type.

Info

Due to the

It implies that:

  • the Source and Destination Users on the Partnership must be allowed to create and link issues on the Source and Destination Project
  • the Destination User on the Partnership is recorded on the target issue history as the issue creator and having linked it
  • the Source User on the Partnership is recorded on the source issue history as the user having linked it
  • the Destination User on the Partnership is set as issue reporter.

Issue Create screen opened via the Herzum Quick action button

4

Complete data on the form, check the Create another box to create more then one issue and click Create.

 

Issue Create screen opened via the Herzum Quick action button

5If the Create another box has been checked, an alert confirm issue successful creation and the screen allows to insert data to create the next issue.

Issue Create screen opened via the Herzum Quick action button

6

Review issues successful creation and linking via JIRA Issue Links as per Link type setting on the Mapping.

Info

Due to the Link type versus setting, the issue link on the source issue reports the Link Type Inward Description.

Issue View screen - JIRA Links panel

 

Precondition: 

  • configure a mapping as per the example below

...

1

Click the Herzum Quick Action button to display the Create Screen of the issue to be created on the Target Project and having the Target Issue Type.

Info

Due to the

It implies that:

  • the logged user must be allowed to create issues on the Destination Project. No linking permission is checked due to the Link Type has been set to Quick Link.
  • the logged user is recorded on the source and target issues history as the user having linked it
  • the logged user is recorded on the target issue history as the user having created it
  • the logged user is set as issue reporter.

Issue Create screen opened via the Herzum Quick action button

 

 2

Review issue successful creation and linking via Quick Link as per Link type setting on the Mapping.

Info

Due to the Link type versus setting, the issue link on the source issue reports the Link Type Outward Description.



Issue View screen - Quick Links panel


When the Link type is set to both, you can expect same behavior described previously but exception is made for the displayed links.

...

The issue view screen of the linked issue display both links to the source issue as well.

 

Create a new issue on a remote JIRA instance and link it 

Restrictions:

  • remote issue linking is allowed for Quick link type only.
  • only issue creation and linking via partnership credentials is allowed
  • the sub-task issue type cannot be set as target issue type.

...

  • configure a mapping as per the example below

    Likewise to the previous examples, the Herzum Quick actions panel shows the button associate to the configured mapping.

    1

    Click the Herzum Quick Action button to display the Create Screen of the issue to be created on the Target JIRA Instance, Project and having the Target Issue Type.

    Info

    The issue is created by applying the Partnership Credential. It implies that:

    • the Source and Destination Users on the Partnership must be allowed to create and link issues on the Source and Destination Project respectively
    • the Destination User on the Partnership is recorded on the target issue history as the issue creator and having linked it
    • the Source User on the Partnership is recorded on the source issue history as the user having linked it
    • the Destination User on the Partnership is set by default as the issue reporter but it can be updated.

    Remote issue create screen

    2If the Create another box was checked the screen allows to insert data to create a new issue.

    Remote issue create screen

Additional facilities

The add-on provides a set of facilities increasing usability:

...