Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,339
Community Members
 
Community Events
176
Community Groups

Problem with automation rule: unable to transfer data to custom fields

When trying to transfer fields from JSM request to Jira Discovery Project only transferred "Summary" & "Description", but my custom fields didn't transfer.
Automation rule log:
Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - My custom fileds*

what could be the problem?

this description didn't help

1 comment

Hi @Tima Ushnitsky

Are you sure the field you have selected in your automation is the correct field in JPD?

JPD works like team managed projects, so fields only exist in the context of their projects. For example, if you manage three software projects, you have three separate fields for 'Story Points' that will appear when configuring automations - same idea for JPD.

The error you are seeing is likely because you have used a field with the same name from another project, which doesn't exist on the JPD issue. To confirm, rename your JPD field to [Field Name]12345 and reconfigure your rule. If you chose the right field originally, [Field Name]12345 will already be selected and you have a different problem. If it is not selected, you have chosen the wrong field and should choose that one in your automation (you can change the name back when you are done).

 

Regards,

- C

HI @Chris Timms 

In JDP you can't choose "paragraph" type for fields, that's why i choose the "short text" type, maybe that's why there are problems? Turns out I can't choose standard Jira types on JDP?Google Chrome_2022-12-07 18-39-16@2x.jpeg

Regards,

- T

Hi Tima, 

As Chris mentionned, Jira Product Discovery is based on team-managed projects and Jira Service Management is based on company manged projects, and that's probably what is causing the error here. 

I have just tested it, and I am getting an error when I am trying to pass a field from a Jira Service Management ticket to a Jira Software team-managed project, and when I try to pass it to a Jira Product Discovery project. So if you are looking to pass a value from one ticket to another, this one won't work. 

However, it is possible to set the value of custom fields directly in the rule and this works well. This rule created an idea in my Jira Product Discovery project which had the value "delighter" for the field named bucket. You could then create conditions, and have different values set according to the request type for example. 

Screenshot 2022-12-07 at 19.35.05.png

If this one isn't working, it might be what Chris suggested, as in my case I have multiple bucket fields, I needed to select the correct one. 

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events