nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I assign an issue using a custom context field?

Sarah Isaacs

Hi ya

I need to assign an issue and maybe the epic to a content writer.

I have created a drop down context field. So that when the Project Lead creates the epic they can chose who will be the writer.

once the Project lead has created the epic and chosen from the drop down. They run a manual trigger. In this automation I want the assignee to become the name(person) who is now in the context drop down field?

I have tried using an edit action - but the field is not a custom field.

I have tried a smart value {{issue.customfield_Content Writer}}

I just can't seem to do it?

Any help would be gratefully received.

Accepted answers

All comments

Jack Brickey

Hi @Sarah Isaacs , I am missing something here. Why would the project lead not simply select the writer by using the Assignee field itself?

John Funk

Hi Sarah,

If I am following you correctly, you have created a custom field for storing a user name. Then you want to run an automation that copies the value of this field into the Assignee field at some point. Correct so far?

But when you are creating the automation rule, you do not see the custom field name when trying to Copy the Assignee from that field. Is that the case?

If so, did you create the custom field in a separate tab or window in your browser and already had your Automation Rules tab open? If so, you will need to publish your rule as is so you don't lose anything. Then refresh the the page and go back into edit the Assignee field. You should see the custom field now.

Sarah Isaacs

Hi @Jack Brickey yes this is a reasonable question. So the name project lead was maybe misleading. As its a Team Leader who will create the Epic. What we want is a dynamic way of assigning the (writer, designer etc) Then every time the various issue types writing, design, illustration and their associated issues(cards) move through production we want the sub tasks assigned to whoever was set up in the initially in the epic in the context custom fields. Is this possible.? sort of like a look up? Thanks any help would be amazing

Sarah Isaacs

Hi @John Funk

Yes you are following correctly.

However the field is a context field. Its just not there no matter what I try.

This is the try to put it in within my manual trigger:

This is a try with the trigger being a value change:

This is the try:

Using a edit issue Fields - as I read a previous post you wrote and thought this might work.

Nothing works.

I've even changed the access to an open project as I wondered if that might be it.

Any help would be amazing. Thanks

Jack Brickey

Ok so looking back at your OP you state "...but the field is not a custom field". If not a custom field what is it? You must've created a custom field that the user can select from drop-down, right? Would you mind providing an image of your automation rule. Also what does the audit log tell you when you try to run the rule.

Sarah Isaacs

@Jack Brickey Hey Jack, Yes this is where I create the fields:

So why I say its not a custom field I mean its not reporter, creator etc.

This is one of the errors I get:

The user has access and is a member. Its all spelt the same.

I'm going to try Initial and surname. But then its not ideal as I'd like their name. Can you covert a Name to the Initial and Surname if that worked. Like dare I say it a look up.

Thanks a million for your help so far

John Funk

I see that you are creating a Sub-task after the auto transition. I assume you want to assignee the issue to the Sub-task and not the trigger issue When you are creating the Sub-task, why not just add the value in the Assignee field?

Click the 3 dots beside the field and click Copy. Then click on the words Current Issue and in the popup that comes, change the Current Issue to Trigger Issue and select the Content Writer field there.

Sarah Isaacs

Hey @John Funk @Jack Brickey

Thanks so much for trying to help me. I'm new to this jira automations thing and so I'm doing my best. So I believe I have tired what you both suggested.

This is what I wanted to do in a nut shell:

1. The Team leader creates a new Epic (which in our project is a book)

2. When they create the epic they fill in the context people fields (writer, Editor, PO, Designer etc)

3. Then they run a manual trigger automation.

The Manual trigger Automation then needs to:
Create a task(writing card)within the epic just created
The Task is called epic name and writing card 1
This task needs to be assigned to the person in the (context people field called Content Writer New)
Then a sub task is created which belongs to the Writing card 1 and so the Epic (name of the book)
Then the sub task is also assigned to the Content Writer New.

I'm a bit lost as to how to do this smart value not a smart value

I'd like the epic to always hold the various job roles and then when I create tasks and then sub tasks to change the assignees to the ones held in the people fields in the epic.

Is this possible please?

Do I need to set up a separate automation that states assignee = People Context field epic?

my knowledge is just not great I'm sorry.

This is my automation so far:

Everything works apart from the assignee.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud