Subtasks do not inherit the "parent's components"

Issue #949 new
Emilia Llorens
created an issue

Hello, we have a problem with the inheritance of Jira's native field "components" from the father to his sub-tasks. We have tried in every way and there has been no way.

We have created a link called "sub-task" and we have also tried but we still can not inherit the "component" or any other field.

Can you help us?

Thank you very much and greetings,

Comments (8)

  1. Fidel Castro Armario repo owner

    Hi @Emilia Llorens,

    You should use Components as source value, instead of "Parent's components", since Components represents the components of current issue (i.e., the parent of the new sub-task), while "Parent's components" represents the components of the father of current issue, which indeed doesn't exist.

  2. Emilia Llorens reporter

    Good Morning,

    we have returned to try as you have indicated (we attach screenshot) and still does not work.

    Can you help us?

    Thank you very much and greetingsherit-parentComponent.PNG

  3. Emilia Llorens reporter

    Good Morning, herit-parentComponent.PNG we have returned to try as you have indicated (we attach screenshot) and still does not work.

    Can you help us?

    Thank you very much and greetings

  4. Emilia Llorens reporter

    Good afternoon,

    We are having problems with the Jira Workflow Toolbox in the post-functions part. Sometimes it works and sometimes not (sometimes if the father transitions according to the state of the daughter and other times it does not), it seems that it is an add-on bug. Since the part of the validations if you are doing them correctly.

    Can you please tell us something about this?

    a greeting

  5. Emilia Llorens reporter

    Good afternoon, we have detected that the post-function "Write field on linked issues or subtasks (write-linked-issues) Writes to a field in linked issues and subtasks fulfilling a condition. "Does not work and all the fields related to the" parent "in the post-functions either.

    We have solved this by using the "Copy parsed ..." and not by calling the fields "execute parent transition", "parent's components".

    We report it as a bug.

    Greetings,

  6. Fidel Castro Armario repo owner

    Hi @Emilia Llorens,

    I need a more detailed description of the bug you have detected.

    Anyway, I think that maybe it's a misunderstanding of the usage of the add-on. "Parent's..." fields only return a value when used from a sub-task. When used from a normal issue it always return null, since a normal issue doesn't have a parent issue. Maybe, this can explain what you think is a bug.

  7. Log in to comment