New Jiras are automatically added to past Sprints

[Daniel Lopez]

Hi there! I'm hoping you can assist me in finding a solution for an unusual issue we're experiencing.

Whenever we create a new Jira in one particular project, the Sprint field is automatically populated with the four most recent sprints. I have thoroughly reviewed the history and automation, but have not been able to identify any potential causes.

Can you help shed some light on what could be happening behind the scenes?

Thanks!

[Trudy Claspill]

Hello @Daniel Lopez 

What type of issue are you creating? Is it an Epic, a standard level issue, or a Sub-task type issue? If they are standard level issues, are they being assigned to an Epic where the Sprint field has those values?

Does the History for such issues document the change to the Sprint field?

What did you look at when you said you have reviewed "automation" specifically?

Have you check the Workflow Transitions to see if there is a Post Function that could be causing this?

Do you have any Listeners configured for your system that might be running a script that causes this?

Do you have any third party apps that provide planning functionality that might be causing this?

[Daniel Lopez]

Hi, answering your questions:

1. It's a standard level issue (a task) assigned to an EPIC not assigned to a Sprint
2. Nope, the History doesn't show anything related to changes in the Sprint field
3. In the project settings menu, we have the Automation section where we have only three rules that never update or set the Sprints
4. No post function apart from the defaults when creating a task, we are using the software simplified workflow
5. No, nothing
6. No

Thanks!

[Bill Sheboy]

Hi @Daniel Lopez 

Would you please post an image of an issue with this symptom, showing the sprint field and complete issue history, in one image?  That may provide some context.  Thanks!

Kind regards,
Bill

[Trudy Claspill]

In addition, there could be a Global automation rule that is making this change.

To see if any automation rules have executed against the issue expand the Automation panel in the issue details view and click the Refresh option.

[Daniel Lopez]

As you can see, we had a lot of sprints assigned to the task

Nothing in the history, though

*sorry, I had to hide the description.

As you can see the task was created on Nov 22nd and it was assigned automatically to 4 completed Sprints in June, July and August

I reviewed the global rules as suggested by Trudy, and we have nothing related to adding or updating the Sprint field.

Thanks

[Trudy Claspill]

Did you check the Automation panel in the issue to see if, after refreshing that, it showed that any rules had been run against the issue?

How are you creating the issue, exactly? Are you using the Create button in the menu bar? Are you using the Create Child Issue within the Epic? Are you Cloning another issue? Are you programmatically creating the issue through the API or from another Automation rule?