New issues are being created with the resolved date set

[Gary McDermott]

I have followed these steps however the problem still exists

https://confluence.atlassian.com/jirakb/new-issues-are-being-created-with-the-resolved-date-set-1167727536.html

All issues are now showing as complete where as they are mid sprint/in progress

Not sure how to resolve this.

Seeking some help please

[John Funk]

Hi Gary,

Check to see if the Resolution field is on the Create screen. If so, remove it. 

[Gary McDermott]

Hi @John Funk 

Assuming you mean make sure its not here? Can confirm not there 

[John Funk]

And you are positive that is the only screen used in your project? Can you post a screenshot of the Issue Type Screen Scheme used on the project? 

[Gary McDermott]

@John Funk please see attached. i have de-selected it from view field config screen for all projects to

[Gary McDermott]

For added context, i have a workflow for service desk, this is for other people of non project access to create/raise tickets, this follow a slightly different journey than the 'working board' scrum workflow which is shared across all projects. I have not been able to identify a common theme as to why these tickets are marking themselves as resolved but its proving to be a real issue as people are now reporting that tickets they have created on service desk are no longer able to see the tickets in their queue but can manually go to the ticket 

[John Funk]

So when you look at the history of the issue, who does it say Resolved the ticket? 

[Gary McDermott]

as soon as a ticket is created, its updating and marking itself as resolved automatically, time time shows that

[John Funk]

That's weird because I don't see an entry for the Resolution getting set. What is the value that gets put in the Resolution field? 

This behavior with it not being in the history tends to lend itself to the the Resolution field being on the Create screen. 

Can you share the details of the Request Fulfillment Screen Scheme?