JIRA REST API can't set a custom post function on transition

Forge
, , ,
1

Hi,

In my Forge App I have defined a custom post function via manifest. It works when I define this post function for a transition in workflow designer, and it is properly triggered on transition.

But, I have an issue when I’m trying to create a workflow with such transition/post function via REST API Create Workflow endpoint.

In the payload I’m setting the post function for transition as

"postFunctions": [
          {
            "type": "ari:cloud:ecosystem::extension/6a3b4c23-de8c-441b-aded-4cc0c7378a5e/0cb091b5-f60c-4481-9b4e-fca4077d46b0/static/grc-post-function"
          },
          {
            "type": "FireIssueEventFunction",
            "configuration": {
              "event": {
                "id": "13"
              }
            }
          }
]

The error message I get is: “Transition “Done” - Rule “ari:cloud:ecosystem::extension/6a3b4c23-de8c-441b-aded-4cc0c7378a5e/0cb091b5-f60c-4481-9b4e-fca4077d46b0/static/grc-post-function” - Unrecognized rule.”

Please advise if this is a proper way to define a post function type.

2

Hi @yurkos1,

have you found a solution for this problem?
Or is it just not possible to set custom post functions via the Workflow API?

Regards
Adrian

3

It seems, adding customPostFunctions created via Forge to a transition is not yet supported by the workflow API: https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-workflows/#forge-rules

@ibuchanan Do you happen to have more information on when this feature could be expected?

And sorry for the direct mention. I hope that you are the right person to talk to about all of this :slight_smile:

Thanks in advance,
Kind Regards
Adrian

4

@AdrianSomesan,

No need to apologize for at-mentions. Unfortunately, I’m not the right person.

What I do know is how “the machine” of Atlassian works and I can point you towards tools & practices that have best chance of yielding results. Even with the gap acknowledged in our docs, that’s not quite enough to make sure we get it done. It certainly leaves you in this current situation where you don’t know where to look for updates or even some projections into the roadmap.

I recommend opening a “suggestion” issue in our open Jira instance in the Ecosystem project. Some additional details might help that get attention: could you explain why the Forge manifest-declared postFunction won’t work for your scenario? That extra detail can help the Jira platform team prioritize. Once you have the appropriate issue key, please report back here. It would be great to have that “feature request” so other folks with a similar need can watch, vote, and comment on that issue.