Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error message Unknown fields set during create (...) Fields ignored - Reporter (reporter)

Estelle Decanis
Contributor
April 29, 2022

Hi,

I want to copy the Reporter from one issue to another. The result is correct but the logs indicate an error. I don't understand what is wrong. Could you help me please ?

 

I put the setting of the automation and the error message :

2022-04-29_12h33_44.png

 

2022-04-29_12h50_51.png

2022-04-29_12h23_48.png

 

 

 

3 answers

1 accepted

1 vote
Answer accepted
Estelle Decanis
Contributor
April 29, 2022

@Nic Brough -Adaptavist- @Sam Bartolome 

I found the problem. Apparently these 2 parameters are in conflict :

2022-04-29_15h25_06.png

I removed all the 'Reporter copy from...' and left only the automation actor precision.

It works without error message :

2022-04-29_15h30_37.png

 

Thank you very much for your help :)

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 29, 2022

This error usually means that the two issues are configured differently.  The source issue is configured to have fields that the destination issue does not support.

So the copy process is trying to copy data to a place that does not exist.

In this case, there are two possibilities:

  • The iissue type that DTS-1217 is has the reporter hidden in the field configuration 
  • There is a custom field called reporter that is valid for DTS-1216, but not DTS-1217
Estelle Decanis
Contributor
April 29, 2022

Hi @Nic Brough -Adaptavist- 

The Reporter field is the native Jira field, no other is created :

2022-04-29_13h39_46.png


In the field configuration the Reporter field is not hidden :

2022-04-29_13h42_54.png

 

Indeed I added in the Edit screen the Reporter field. 

2022-04-29_13h50_42.png

 

I have a new test but the error message is still there

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 29, 2022

Ok, not a custom field, so the question is now what are the issue types of DTS-1216 and DTS-1217, and what do their field configurations say about reporter

The message you are getting is telling us that reporter is hidden for the DTS-1217 issue type.  (There might also be a quirk coming from the permissions here - if the reporter of DTS-1216 no longer has permission to create issues in the DRS project, it might be failing on that)

Like Sam Bartolome likes this
Estelle Decanis
Contributor
April 29, 2022

The output type DTS-1216 is a 'Folder' and the output type DTS-1217 is an 'Epic'. When you look at the field configurations they are identical.

The automation performs the modification of the Reporter. So the permission is ok. However I checked, there are 2 project role : 

2022-04-29_14h45_44.png

I tested with each of them and I still have the error message

0 votes
Sam Bartolome
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 29, 2022

Hi @Estelle Decanis ,

My understanding of the error suggests that the issue types DTS-1216 and DTS-1217 are different and even reporter is a needed field for any issue creation, it seems that it may not be configured on the field configuration.

Are different issue types or the same? If different, please check the field configuration for differences and the workflow for conditions

Estelle Decanis
Contributor
April 29, 2022

Hi @Sam Bartolome 

These are different issue types. The field configurations are the same :

2022-04-29_14h14_55.png

 

2022-04-29_14h16_39.png

 

and these 2 issue types are in the same workflow :

2022-04-29_14h18_24.png

 

2022-04-29_14h19_28.png

 

2022-04-29_14h20_11.png

I do not see the origin of the error

Suggest an answer

Log in or Sign up to answer