Summary:
I have 2 projects, 1 business oriented and 1 team oriented. The business project works with Initiatives and Epics, the Team project works with Stories, Bugs, Tasks etc.
Within the whole company we work with different domains, such as E-Commerce, Supply Chain, Finance etc. The Epics / Initiatives have a Custom field where we specify the Domain the Epic is linked to. The teams create Stories for these Epics to work on (within the fore mentioned team project) and link them to the Epic.
Problem:
What I want is that the Stories that are created in the Team project, automatically inherit the Domain-field value from the linked Epic. I want to achieve this for every new story created but also existing Stories (as I am trying to improve transparency).
Through automations I only seem to be able to specify 1 particular value and not any value. But maybe I am doing something wrong.
@Peter Did you get an answer to this? I am experiencing a similar problem - trying to inherit a field from one project to another. As I am writing automation, it appears the branch is restrictive to the project I am writing the automation on, with no ability to change/add (not even available under the rule details)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Peter
Please provide here an image that shows your Automation Rule. We can't provide guidance without those details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you also show on what you have done in automation, so that we can improve it further
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.