Is it possible to set a default creator value

[Ben Gallimore]

Hi there

I have a scenario where I use an internal Jira board with multiple customer projects (Internal), and a separate instance that we share with the customer (External), the tasks in the project are synchronised by the use of the sync tool (Backbone Sync).

As the clients do not have accounts in the internal jira instance, the sync tool errors out when the clients log a task in the external board. 

Backbone sync allows us to set a default reporter, however it cannot set the creator id.

Is it possible to set a default creator, either at the instance level? or preferably based on the method of creation?

[elizabeth_jones · Accepted solution]

@Ben Gallimore check out this thread and see if it helps solve your

challenge: https://community.atlassian.com/t5/Jira-questions/The-issue-creator-as-default-assignee-how-to/qaq-p/342907

[Ben Gallimore]

Sorry @elizabeth_jones but this article seems to be showing how to use the creator field not set it.  

My question is fairly simple, is it possible to set the field?  Using a tool like they suggest - script runner, or using automation.

I am suspecting the creator field (at least on cloud) is a protected / locked field.

[elizabeth_jones]

Here are the smart values that can be set: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/

{{creator}}

The user who created the active issue. It is not possible to change the creator of an issue.

1 {{creator.displayName}}

If i'm understanding this correctly, the answer is no. 

[Ben Gallimore]

Thanks @elizabeth_jones 

[francis]

Hi  @Ben Gallimore - is the internal jira on Jira Cloud, or on premise

[Ben Gallimore]

Jira Cloud - sorry for the delay in responding

[kuldeep Singh]

Hi @Ben Gallimore ,

For customer ticket creation we suggest you to configure a Incoming email server, this will help you a lot in creating the customer ticket directly into the Jira,

https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/

Thanks.

[Ben Gallimore]

Hi @kuldeep Singh 

Thanks for the response, I do understand the email process, and have previously set up this workflow.

However we use a combined board for more reasons than just creating the ticket, it is used in our DevOps processes with our clients so they can help our Scrum Master define prioritisation of work in progress and work awaiting commencement.  

Asking them to exit the board and create a ticket using an email is a sub-optimal user experience.