Versions Compared

Old Version 1

changes.mady.by.user Jonathan Muse

Saved on

compared with

New Version Current

changes.mady.by.user Shane Smith

Saved on

Key

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

Problem

Often a body of work is not able to be captured within a single issue in Jira since it requires Sometimes, a task or project spans across multiple teams or business units to accomplish. Information , making it challenging to capture all the relevant information in a single Jira issue. When details are added to a ticket in one teams project does not automatically flow through to the other teams project and important updates can become lostteam's project, they don't automatically transfer to another team's project, leading to the loss of important updates.

Solution

To solve address this problemissue, you can use a listener script from Power Scripts can be used to add . This script adds new comments from one teams team's project to the corresponding issue in another project.

Step 1: Create the script

  1. Create a script, similar to the one below to be called by the listener

    Code Block
    string [] links = linkedIssues(key, "Cloners");

if(size(links) > 0) {   
    JComment lastComment = getLastComment(links[0]);
    addComment(clone, lastComment.author, lastComment.text, lastComment.securityLevel);
}
Info

The above script finds the corresponding issue by using links. This script uses the “Cloners” link type specifically but any link type can be used. Please note that the link type name should be used. This name is different the outward and inward link descriptions. For example, with the Cloners link type The link type names can be found on the Issue Linking page in the Jira admin. In the example of the "Cloners" link type, the outward description is “clones” "clones," and the inward is "is “is cloned by” by," but the name for the link type is “Cloners”. The link type names can be found on the Issue Linking page in the Jira admin."Cloners."

Info

The above script assumes that there should only be one link of type “Cloners” "Cloners" for the issue since the issue can only be cloned from a single source. If using a different link type, the script will select the first link it finds for the given type.

Step 2: Configure the listener

  1. Go to Power Apps Config > Power Scripts > Listeners.

  2. Click the Add listener

Multiple issue types can be added to the issue type filter

  1. After selecting a script button.

  2. Select the script created above for the listener , choose the event the listener should respond to. Only issue specific events like Issue Created, Issue Updated, etc. can then be filtered by project and issue type.

  3. After selecting an issue specific event the input form will update with the new controls for filtering:

  4. The project and/or issue type filters can then be applied:

  5. Click the Add button to complete the setup of the listener

Info

Note:

  • Both the project and issue type filters can be set independently, they are not needed together

  • Multiple projects can be added to the project filter

    1. script.

      1. Leave the Asynchronous option unchecked.

    2. Leave the user input blank.

    3. Select Issue Commented for the event type.

    4. Optionally, add a project and issue type filter to limit the listener to specific project/issue types.

      Image Added

    5. Click Add to save the listener.

    Info

    The script attempts to add the comment to the linked issue using the same user profile as the user who created the original comment. If that user lacks permissions to edit issues in the linked project, another user profile can be used as the author for the comment. Modify line 5 of the script accordingly.

    Table of Contents

    Table of Contents