Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


JIRA Miscellaneous Workflow Extensions for Cloud

We migrated from JIRA Server to JIRA Cloud recently.

When we are trying to change the status of an issue (ex: in progress to resolved) the following message is shown:

"It seems like you have a post function from the JIRA Misc Workflow Extensions add-on, but the add-on isn't installed. Please remove all post functions from this add-on from your workflows"

1. is there a resolution for this?

2. will installing the JMWE for cloud fix this?

2 answers

1 vote
David Fischer _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 23, 2019

Atlassian made migrating from Jira Server to Jira Cloud really difficult. Even when apps exist for both platforms (which is the case for JMWE), you still need to adjust your workflows. See for details.

0 votes
Hernan Halabi - Elite IT Consulting Group
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 22, 2019

Hi @Sneha Philip the resolution would be to edit the workflow and remove the post function that comes from server. Installing the add-on most likely won't fix this since even though you can do the same that you configured in server, most likely there will be a different way to set that up, therefore it will continue to fail

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events