nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JMWE Subtasks are created automatically but the issue screen isn't updating to show newly created

Javanshir Mustafayev _ HIT

Subtasks are created automatically but the issue screen isn't updating to show newly created subtasks.

I'm using JMWE to create a subtask out of a subtask when the previous subtask is closed. This is a process and I wish the user to see the newly created subtask when it was created.

Is this possible?

I've tried to use JMWE setting 'navigate to the newly created issue' but this only works if you are in the issue view mode. My users are in the parent issue view so this isn't working.

Accepted answers

Suprija Sirikonda _Appfire_

Hi @Javanshir Mustafayev _ HIT ,

Unfortunately, this is not possible because of a Jira limitation.

-Suprija

All comments

Suprija Sirikonda _Appfire_

Hi @Javanshir Mustafayev _ HIT ,

Unfortunately, this is not possible because of a Jira limitation.

-Suprija

Javanshir Mustafayev _ HIT

Hi @Suprija Sirikonda _Appfire_

The page is being updated when the parent issue changes its status, maybe if I trigger a status change for the parent on each subtask creation for example from In progress to In progress this helps?

David Fischer

Hi @Javanshir Mustafayev _ HIT ,

The problem is that, when you use the Jira Cloud REST API to create a new sub-task (or even if you manually create the sub-task from another browser tab), Jira Cloud doesn't automatically refresh any issue view open on the parent issue (to show the newly-added sub-task). And unfortunately, Jira Cloud doesn't include any mechanism for an app (such as JMWE) to trigger any kind of action on the user's browser either.

JMWE includes a "hack" that allows it to still trigger some actions on the browser based on post-function outcomes, and this is how it supports the "Navigate to new issue" option, as well as the "Display message to user" post-function. Unfortunately, this hack has a lot of limitations (mostly for performance reasons) and one of them is that it only receives "commands" for the current issue (the issue being displayed).

I don't believe there is any workaround, unfortunately.

David

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

jira-misc-workflow-extensions