reporter

[Marzi Goodarzian]

Hi

Is possible a project member can create issue and The created issue is reported from another reporter ? (There is no way to change the reporter in create screen  for the project's member).

It happened when issue was created .

[Nic Brough -Adaptavist-]

Add the reporter field to the create screen, and make sure the people creating the issue have the permission "change reporter"

[Marzi Goodarzian]

No...

I do not mean this.

as a example:

user1 created issue and now reporter of same issue is another user(user2)!!!

This despite the fact that there is not any field of change reporter in create screen and no any one have "modify reporter" permission.

even there is in notification email that user2 create issue!!and this email send to user2.

this is my problam.

[Nic Brough -Adaptavist-]

That's nothing like your original question.

Now you are saying that the reporter of an issue has been changed after it was created.  That's simple to work out how - look at the issue history, it will tell you when the reporter was changed, and by whom.

[Marzi Goodarzian]

Oh No...

It happened when issue was created.

Reporter dont Changed after issue creation !!change reporter and issue creation happened Simultaneously, without "change reporter" field in create screen.

[Nic Brough -Adaptavist-]

Ok, so to be clear, what you are seeing is:

• You have two users, A and B. 
• A creates a new issue
• There is no reporter field on screen for A
• The issue is created, showing B as the reporter

If that is the case, then you have a script or automation in a post-function that is changing the reporter field.

[Marzi Goodarzian]

Hi @Nic Brough -Adaptavist- thanks for answer.

but this workflow shared between several project, and This workflow has not changed for months, this problam happen only one day for few issues! 

However I reviewed the items you mentioned again.

Is there any other reason?

thanks

[Nic Brough -Adaptavist-]

I am not sure, you have not confirmed that my description of what you are seeing is correct.

[Marzi Goodarzian]

Your description is right. 

In addition to your description, all notification email sent to B.

[Nic Brough -Adaptavist-]

Ok, great. 

That narrows it down to one of two things:

1.  The reporter field is on screen, the user creating the issue has "change reporter" permission, and they have used it.  Note that when other people try the same, if they do not have "change reporter", they won't get the field.  That applies to you as an admin too - you might not be seeing it if you don't have the project permission.

2. You have an automation, post-function or listener changing the reporter as the issue is created.

It doesn't matter if the workflow has changed, or that it is shared.  The reporter field is separate to the workflow, and the workflow only holds the post-function (if it is that) on the create transition.  Listeners and automations are triggered by the workflow firing events, but are not part of the workflow.

[Marzi Goodarzian]

Thanks @Nic Brough -Adaptavist-

[Marzi Goodarzian]

There is a question:

Is there a reason for change reporter to B? Why was not reporter change to C or other users?

[Nic Brough -Adaptavist-]

You would have to ask the person who set it (either the person entering the issue, or what they configured in the automation/post-function/listener)

[Marzi Goodarzian]

Thanks