One of our end users is running into an issue in that when she creates a JIRA issue (ticket), it automatically marks it as resolved when it is not. What could be causing this to occur?
You may have already checked, but do you have any automation rules running that may have picked this up? Potentially on certain criteria for this particular user/organisation, or criteria, that they are using specifically when raising the ticket?
I'd be interested to see, if you can see the ticket history - does this show 'who' resolved the ticket? As if it is automation, it may either be set to the triggering user, a particular user who created an automation rule, or even "automation by Jira".
Worth something to rule out if you haven't already.
The usual problem here is that an inexperienced admin has put the resolution field on the create screen. So you end up creating resolved issues.
Could you check if the resolution is asked for when you create an issue of that type in the project?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events