Set component field while creating subtasks

Issue #480 resolved
Maximilian Peter created an issue

I'm trying to configure a function to create a subtask. The component-field of the subtask should be set with the value of another customfield "Teilbereich" (Drop-Down / Single Value) from the parent issue. The values of the field "Teilbereich" are the same values like in the component-field.

I implemented a transition "Action1" with the function"Create issues and subtasks" with the following configuration:

1.png

During the transition there is a screen with the customfield "Teilbereich" and the user is able to select the value for "Teilbereich.

My problem is: If I execute the transition "Action 1", I get a error message with the following text:

"Error occurred while creating issue. This could be due to a plugin being incompatible with this version of JIRA. For more details please consult the logs, and see: http://confluence.atlassian.com/x/3McB com.atlassian.jira.issue.customfields.option.LazyLoadedOption cannot be cast to java.util.Collection"

If I delete the copy action for the field "component" the creation of the subtask works well.

May you help me solving this issue? Greets Max

Comments (7)

  1. Fidel Castro Armario repo owner

    Hi Max,

    Is field "Teilbereich" a standard JIRA Select List? Please, tell me the type of field it is.

    Try the following workaround: try setting "Components" using a "Parsed text (basic mode)" containing only the field code of Teilbereich custom field.

    This way we are generating a text value with the name of the component in Teilbereich, and the plugin will try to convert it into a valid Component value.

  2. Maximilian Peter reporter

    Hi Fidel,

    Teilbereich is a standard JIRA select list (Single select).

    If I use the "Parsed text (Basic mode)" it works. But for the subtask creation it doesn't work.

    Greets Max

  3. Fidel Castro Armario repo owner

    I have achieved to reproduce the problem, and I don't have any problem to make it work using the workaround for sub-task creation. It's working fine for me.

    I don't understand what you mean when you say it works, and then say it doesn't work for sub-task creation. In which cases it's working for you?

  4. Maximilian Peter reporter

    I'm sorry, it was my fault. I missunderstood your solution. I created a new action "copy parsed text to field" and didn't use the "parsed text" function in the "create subtask" function.

    Thanks for your help.

    Greets Max

  5. Fidel Castro Armario repo owner

    Hi Max,

    I have fixed the problem in version 2.2.29_beta_1. Please, try your original configuration and tell me whether it solves your problem.

    Thanks

  6. Log in to comment