Unable to clone a custom issue type due to regex post transition
I have a post transition on Create for a custom issue type that uses regex to determine the assignee. When I remove this logic I am able to successfully clone the issue.
The field Assignee will be set according to the evaluation of Database Management System against the following set of rules: (^Oracle$)Oracle DBAs (^MySQL$)MySQL DBAs (^MongoDB$)MySQL DBAs
Comments (10)
-
repo owner -
repo owner Hi Elizabeth, I close the issue after 1 month open without news. Please, reopen it if you keep having the problem, and you can provide some of the information I asked you for in my first comment.
Regards
-
repo owner - changed status to closed
-
reporter - changed status to open
Apologies, I have been out of town.
Jira v6.1.5 Database Management System is a Select List (single choice) custom field.
There is no error message in the UI. It appears to create a clone and creates a clone link in the ticket but that link is a link to itself.
-
repo owner I need to reproduce the problem in order to fix it, but until the moment I haven't been able to do it. I would like to see the full list of post-functions you are executing at issue creation. Can you please attach a screenshot of post-functions tab in configuration screen of transition "Create Issue"?
BTW, have you tried to reproduce the problem using version 2.1.21 of the plugin?
-
reporter Screen shot is attached. I put in a request to have the plugin upgraded but it has not been prioritized by the system adminstrator.
Thank You!
-
repo owner Post-function "Create the issue originally" should be in first place in execution order. I think that simply by doing that change the problem will be solved.
-
repo owner By the way, in your third post-function you can use + Database in order to add the label Database without overwriting any other labels previously introduced.
-
reporter You are right, it works! Thank you!
-
reporter - changed status to resolved
fixed
- Log in to comment
Hi Elizabeth,
I have tried to reproduce your problem using version JIRA Workflow Toolbox 2.1.19 and JIRA 6.3.4, and a Select List custom field in parameter Field to be checked..., but haven't found any problem. In my case everything seems to work correctly.
I would need the following information in order to reproduce your problem:
BTW, have your checked whether the problem persists using recently released version 2.1.20 of JIRA Workflow Toolbox?