Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JMWE - Create / Clone Issue(s) Post-function do not select parent issue

Hi. I'm using Create / Clone Issue(s) Post-function to create issues conditionally and there is "Parent Issue" option. I do not want to select a parent issue for newly created issues.

Putting null or not putting anything there results in

ERROR jadmin 788x9789x2 fdhlyq 10.0.0.189 /secure/WorkflowUIDispatcher.jspa [c.a.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 21 from workflow 270802 on issue 'AP-41'
com.opensymphony.workflow.WorkflowException: An error occurred while executing a Create / Clone Issue(s) post-function: Create Issue post-function: calculated parent issue should be a String : root cause: Create Issue post-function: calculated parent issue should be a String

 

2 answers

1 accepted

0 votes
Answer accepted

Can you share a screenshot of the post function configuration?

parentIssueNull.PNGparentIssueEmpty.PNG

 

Both result in said error

I meant the whole post function configuration, to see why the patent issue option appears. I'm any case, you can try changing from "calculated" to another option, it will get rid of the error. 

I've selected "Another Issue" option and didn't fill in the field (no issue seleceted) and this config still results in same error

Full post function:

issueCreateFull1.PNG

issueCreateFull2.PNG

Did you try with the default value when you select "Calculated" as the issue type, which is "Current issue"?

Unless you are creating a sub-task (which the post function cannot know since the issue type is calculated at runtime), the parent issue will be ignored.

Well the thing is that newly created issues must not have a parent issue

Ok so this kinda worked. But

Calculated issue type script has 2 possible outcomes - for 1st issuetype everything works fine, but 2nd issuetype create function results in missing fields error for some reason though both issuetypes share same fields and even screens. Only difference is workflow

An error occurred while executing a Create / Clone Issue(s) post-function: Issue could not be created because of validation errors: Reason(s): VALIDATION_FAILED Field error(s): Field customfield_10225: is required. Field customfield_10226: is required. Field customfield_10218: is required.

All 3 customfields are set in  Set fields of new issue section of the post function (Groovy scripted). I have no idea why is this happening

It could be because these custom fields don't appear on the Create screen for the issue type. I recommend you try to manually create an issue of the second issue type and make sure you can pass all the required fields.

Hi @David Fischer _Innovalog_ ,

When transitioning the ticket to assign it to a project by selecting a project on the transition screen, customer get the following error:

An error occurred while executing a Create / Clone Issue(s) post-function: Issue could not be created because of validation errors: Reason(s): VALIDATION_FAILED Field error(s): Field issuetype: The issue type selected is invalid. : root cause: Issue could not be created because of validation errors: Reason(s): VALIDATION_FAILED Field error(s): Field issuetype: The issue type selected is invalid.

Validator error.png

 

When they retry to transition but by assigning to another project, that goes well.

The error message is referring to validator. The transition contains 2 validators created with JMWE which I've already checked. 

Can you help us with this problem?

Hi @Zehra Atmaca ,

the error message is not actually related to a Validator. The problem is in the Create/Clone Issue(s) post-function that's placed on the transition that is specifying an invalid issue type. It's probably because the issue type is not valid for the destination project.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

857 views 30 33
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you