[JSWSERVER-13530] Backlog doesn't show issues in the correct sprints

Type: Bug
Resolution: Fixed
Priority: High (View bug fix roadmap)
Fix Version/s: 7.2.7
Affects Version/s: 7.0.0, 7.1.0, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.6
Component/s: None
Labels:

Introduced in Version:
7
Support reference count:
87
Symptom Severity:
Severity 2 - Major
UIS:
511
Bug Fix Policy:
View Atlassian Server bug fix policy

Summary

The Agile Backlog doesn't show issues in the correct sprints. Moving issues to sprints reverts back after refreshing the page.

Cause

The scenario mentioned below is only an example of the scenario where this issue occurs. There could be more causes for this problem. We are working on our side on identifying more causes.

The index is not reindexing changes to the Sprint correctly because there is, or used to be, another field called "Sprint" with a different data type.
Because the Backlog uses the index, although the issues are correctly modified on the backend, they are displayed incorrectly on the boards.
There are reports that customers on JIRA 7.2 have run into this despite not having another "Sprint" field. Exact cause is still unknown.

Check if affected:

This DB query returns issues affected by this:

select p.pkey ||'-'|| i.issuenum as key, ci.field, ci.newvalue, ci.newstring from changegroup cg join changeitem ci on cg.id = ci.groupid left join jiraissue i on cg.issueid = i.id left join project p on i.project = p.id where ci.field = 'Sprint' and newvalue is NULL;

For MySQL use:

select  CONCAT(p.pkey, "-", i.issuenum)AS 'Issue key', ci.field, ci.newvalue, ci.newstring from changegroup cg join changeitem ci on cg.id = ci.groupid left join jiraissue i on cg.issueid = i.id left join project p on i.project = p.id where ci.field = 'Sprint' and newvalue is NULL;

Environment

JIRA Software Cloud and Server

Steps to Reproduce

Create a Custom Field type "labels" and name it "Sprint"
On a certain issue add a label and remove a label
On the backlog view, move that issue to a different sprint

There are reports that customers on JIRA 7.2 have run into this despite not having another "Sprint" field. Exact cause is still unknown.

Expected Results

Issue is correctly moved between sprints and changes persist.

Actual Results

The issue is dragged over to the sprint.
The below exception is thrown in the JIRA log: Error indexing issue

2016-04-11 10:52:07.559050500 2016-04-11 10:52:07,548 http-nio-3000-exec-10 WARN sysadmin 652x1263x1 9aomkb 103.233.242.8 /rest/greenhopper/1.0/sprint/rank [c.a.j.issue.index.DefaultIssueDocumentFactory] Error indexing issue BDBPP-145: Dropping 'customfield_10402'
2016-04-11 10:52:07.559053500 java.lang.NullPointerException
2016-04-11 10:52:07.559054500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory.movedToSprintAfterStartDate(SprintHistoryEntryFactory.java:217)
2016-04-11 10:52:07.559055500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory.lambda$null$6(SprintHistoryEntryFactory.java:188)
2016-04-11 10:52:07.559093500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory$$Lambda$633/11364990.apply(Unknown Source)
2016-04-11 10:52:07.559095500 	at java.util.Optional.map(Optional.java:215)
2016-04-11 10:52:07.559095500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory.lambda$removeOtherNonActiveSprints$7(SprintHistoryEntryFactory.java:188)
2016-04-11 10:52:07.559102500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory$$Lambda$631/2285389.test(Unknown Source)
2016-04-11 10:52:07.559103500 	at java.util.Collection.removeIf(Collection.java:414)
2016-04-11 10:52:07.559104500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory.removeOtherNonActiveSprints(SprintHistoryEntryFactory.java:185)
2016-04-11 10:52:07.559111500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory.getSprintChangeHistoryForIssue(SprintHistoryEntryFactory.java:154)
2016-04-11 10:52:07.559112500 	at com.atlassian.greenhopper.customfield.sprint.SprintHistoryEntryFactory.getSprintChangeHistory(SprintHistoryEntryFactory.java:52)
2016-04-11 10:52:07.559114500 	at com.atlassian.greenhopper.customfield.sprint.SprintCustomFieldIndexer.addDocumentFields(SprintCustomFieldIndexer.java:45)
2016-04-11 10:52:07.559118500 	at com.atlassian.greenhopper.customfield.sprint.SprintCustomFieldIndexer.addDocumentFieldsSearchable(SprintCustomFieldIndexer.java:30)
2016-04-11 10:52:07.559120500 	at com.atlassian.jira.issue.index.indexers.impl.AbstractCustomFieldIndexer.addIndex(AbstractCustomFieldIndexer.java:40)
2016-04-11 10:52:07.559121500 	at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.add(DefaultIssueDocumentFactory.java:84)
2016-04-11 10:52:07.559126500 	at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.addAll(DefaultIssueDocumentFactory.java:75)
2016-04-11 10:52:07.559127500 	at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.apply(DefaultIssueDocumentFactory.java:50)
2016-04-11 10:52:07.559133500 	at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.apply(DefaultIssueDocumentFactory.java:30)
2016-04-11 10:52:07.559134500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer$DefaultDocumentCreationStrategy.get(DefaultIssueIndexer.java:553)
2016-04-11 10:52:07.559135500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer.lambda$reindexIssues$1(DefaultIssueIndexer.java:166)
2016-04-11 10:52:07.559140500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer$$Lambda$593/22309686.perform(Unknown Source)
2016-04-11 10:52:07.559141500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer.lambda$null$2(DefaultIssueIndexer.java:305)
2016-04-11 10:52:07.559142500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer$$Lambda$600/4056176.get(Unknown Source)
2016-04-11 10:52:07.559143500 	at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:7)
2016-04-11 10:52:07.559147500 	at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:5)
2016-04-11 10:52:07.559148500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer.lambda$perform$3(DefaultIssueIndexer.java:303)
2016-04-11 10:52:07.559150500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer$$Lambda$594/28919328.consume(Unknown Source)
2016-04-11 10:52:07.559156500 	at com.atlassian.jira.util.collect.CollectionUtil.foreach(CollectionUtil.java:39)
2016-04-11 10:52:07.559157500 	at com.atlassian.jira.util.collect.CollectionUtil.foreach(CollectionUtil.java:52)
2016-04-11 10:52:07.559158500 	at com.atlassian.jira.issue.util.IssueObjectIssuesIterable.foreach(IssueObjectIssuesIterable.java:24)
2016-04-11 10:52:07.559159500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer.perform(DefaultIssueIndexer.java:282)
2016-04-11 10:52:07.559163500 	at com.atlassian.jira.issue.index.DefaultIssueIndexer.reindexIssues(DefaultIssueIndexer.java:162)
2016-04-11 10:52:07.559165500 	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:541)
2016-04-11 10:52:07.559166500 	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:517)
2016-04-11 10:52:07.559167500 	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:500)
2016-04-11 10:52:07.559174500 	at com.atlassian.jira.issue.index.DefaultIndexManager.release(DefaultIndexManager.java:489)
2016-04-11 10:52:07.559175500 	... 3 filtered
2016-04-11 10:52:07.559176500 	at java.lang.reflect.Method.invoke(Method.java:497)
2016-04-11 10:52:07.559176500 	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:22)
2016-04-11 10:52:07.559182500 	at com.sun.proxy.$Proxy11.release(Unknown Source)
2016-04-11 10:52:07.559183500 	... 3 filtered

A refresh of the backlog shows the issue back on the previous location.

Notes

The problem is related to historic events. It will only affect issues that have the duplicate "Sprint" field cleared in the past. New issues where labels weren't modified, won't have the problem.

Workaround

Please be aware that unfortunately the workaround here is temporary and the issue comes back after some time

Always generate backup of your database before making any changes to it via SQL. Any workaround requiring SQL changes carries inherent risk so a backup of your DB is essential to restore working conditions if there is a critical problem. This workaround should be tested in a clone of your Production environment prior to attempting it in Production.

Backup all the "sprint-removal history items" into a separate table, and remove them from the initial table

create table changeitem_quarantine_jira721 as
select ci.* from changeitem ci
where ci.field = 'Sprint'
and   ci.newvalue is null;

Remove them from the initial changeitem table:

DELETE from changeitem ci where ci.id in (select id from changeitem_quarantine_jira721);

Restart JIRA
Full/Locked reindexing

If any misbehaviour happens, the records can be restored again with the statement:

insert into changeitem
select * from changeitem_quarantine_jira721 where id not in (select id from changeitem);

is caused by

JSWSERVER-12805 Velocity Report Should Only Show Sprints Related To The Current Board

Closed

links to

GHS-61674

mentioned in: Page Failed to load; Page Failed to load; Page Failed to load; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

was cloned as: JSB-180 Loading...

(6 mentioned in, 1 was cloned as)

Form Name

Susmita Jha added a comment - 18/Mar/2021 8:56 AM - edited

I am facing this in Jira version 8.5.8.

Atlassian Ticket raised - GHS-217202

Susmita Jha added a comment - 18/Mar/2021 8:56 AM - edited I am facing this in Jira version 8.5.8. Atlassian Ticket raised - GHS-217202

Andreas Lindquist added a comment - 12/Aug/2020 1:24 PM

We are using v8.4.1#804002 and is also experiencing this issue.

Andreas Lindquist added a comment - 12/Aug/2020 1:24 PM We are using v8.4.1#804002 and is also experiencing this issue.

Koel Misra added a comment - 04/Feb/2020 4:39 PM

We are using v8.5.3#805003-sha1:b4933e0 and are still seeing this issue. Is there anything that can be done.

Koel Misra added a comment - 04/Feb/2020 4:39 PM We are using v8.5.3#805003-sha1:b4933e0 and are still seeing this issue. Is there anything that can be done.

Roy Schumacher added a comment - 26/Aug/2019 1:51 PM

we are using v8.2.3#802003 and the issue is still present.

anyhing we can do?

does it depend on the index structure? sometimes re-indexing helps for some days.

Roy Schumacher added a comment - 26/Aug/2019 1:51 PM we are using v8.2.3#802003 and the issue is still present. anyhing we can do? does it depend on the index structure? sometimes re-indexing helps for some days.

Deleted Account (Inactive) added a comment - 16/Feb/2017 8:50 AM

We solved the problem with a database query on the changeitem table.

We found some data which had the content 'null'

We changed the content to an empty string like: ""

You should have a testsystem, a database admin and of course: a full backup of your JIRA installation!!

Deleted Account (Inactive) added a comment - 16/Feb/2017 8:50 AM We solved the problem with a database query on the changeitem table. We found some data which had the content 'null' We changed the content to an empty string like: "" You should have a testsystem, a database admin and of course: a full backup of your JIRA installation!!

Craig Solinski added a comment - 15/Feb/2017 10:30 PM - edited

Hello, I thought we were beyond the problem, we had it with 724 and it was gone after upgrading to 727 BUT its suddenly happening again on 727.

Craig Solinski added a comment - 15/Feb/2017 10:30 PM - edited Hello, I thought we were beyond the problem, we had it with 724 and it was gone after upgrading to 727 BUT its suddenly happening again on 727.

Paulius Sitkevicius added a comment - 01/Feb/2017 12:15 PM

Hello Peter, after upgrade to 7.2.7 we haven't faces this error any more, from our perspective it is fixed in 7.2.7

Paulius Sitkevicius added a comment - 01/Feb/2017 12:15 PM Hello Peter, after upgrade to 7.2.7 we haven't faces this error any more, from our perspective it is fixed in 7.2.7

Rytis Budreika added a comment - 01/Feb/2017 11:34 AM

Hello Peter, as far as I know issue was fixed in 7.3.0 version, though did not test it yet.

Rytis Budreika added a comment - 01/Feb/2017 11:34 AM Hello Peter, as far as I know issue was fixed in 7.3.0 version, though did not test it yet.

Deleted Account (Inactive) added a comment - 01/Feb/2017 10:56 AM

Thank you to everyone who share knowledge on the page.

We ran in this issue too: Having a JIRA 6.3.12, perfom an update on a testsystem to 7.2.3 and running into the indexing Problem too: Error indexing issue xxxxx-123: Dropping 'customfield_10007' (the sprint customfield). The SQL Query shows a lot of Issues when we excuted it.

Today I tried another update on the test system: I installed a 7.2.7 and imported my 6.3.12 data.
As I understand the conversation on this page, the error should be fixed in 7.2.7

I still get errors. Was anyone successful and can confirm that 7.2.7 fixes the error?

Deleted Account (Inactive) added a comment - 01/Feb/2017 10:56 AM Thank you to everyone who share knowledge on the page. We ran in this issue too: Having a JIRA 6.3.12, perfom an update on a testsystem to 7.2.3 and running into the indexing Problem too: Error indexing issue xxxxx-123: Dropping 'customfield_10007' (the sprint customfield). The SQL Query shows a lot of Issues when we excuted it. Today I tried another update on the test system: I installed a 7.2.7 and imported my 6.3.12 data. As I understand the conversation on this page, the error should be fixed in 7.2.7 I still get errors. Was anyone successful and can confirm that 7.2.7 fixes the error?

AlanR added a comment - 20/Jan/2017 11:16 AM

Hi Leonard, Thanks for sharing. We have this same problem and have come to the same conclusion. We are preparing to do this in our production environment.

AlanR added a comment - 20/Jan/2017 11:16 AM Hi Leonard, Thanks for sharing. We have this same problem and have come to the same conclusion. We are preparing to do this in our production environment.

Assignee:: Artur Pawelczyk (Inactive)

Reporter:: Mauro Badii (Inactive)

Affected customers:: 96 This affects my team

Watchers:: 158 Start watching this issue

Created:: 14/Apr/2016 4:40 AM

Updated:: 17/Jan/2025 12:36 PM

Resolved:: 29/Dec/2016 3:47 PM

Details

Description

Summary

Cause

Environment

Steps to Reproduce

Expected Results

Actual Results

Notes

Workaround

Attachments

Issue Links

Forms

Activity

Collapse comment: Susmita Jha added a comment - 18/Mar/2021 8:56 AM, Edited by Susmita Jha - 18/Mar/2021 2:01 PM

Expand comment: Susmita Jha added a comment - 18/Mar/2021 8:56 AM, Edited by Susmita Jha - 18/Mar/2021 2:01 PM

Collapse comment: Andreas Lindquist added a comment - 12/Aug/2020 1:24 PM

Expand comment: Andreas Lindquist added a comment - 12/Aug/2020 1:24 PM

Collapse comment: Koel Misra added a comment - 04/Feb/2020 4:39 PM

Expand comment: Koel Misra added a comment - 04/Feb/2020 4:39 PM

Collapse comment: Roy Schumacher added a comment - 26/Aug/2019 1:51 PM

Expand comment: Roy Schumacher added a comment - 26/Aug/2019 1:51 PM

Collapse comment: Deleted Account (Inactive) added a comment - 16/Feb/2017 8:50 AM

Expand comment: Deleted Account (Inactive) added a comment - 16/Feb/2017 8:50 AM

Collapse comment: Craig Solinski added a comment - 15/Feb/2017 10:30 PM, Edited by Craig Solinski - 15/Feb/2017 10:31 PM

Expand comment: Craig Solinski added a comment - 15/Feb/2017 10:30 PM, Edited by Craig Solinski - 15/Feb/2017 10:31 PM

Collapse comment: Paulius Sitkevicius added a comment - 01/Feb/2017 12:15 PM

Expand comment: Paulius Sitkevicius added a comment - 01/Feb/2017 12:15 PM

Collapse comment: Rytis Budreika added a comment - 01/Feb/2017 11:34 AM

Expand comment: Rytis Budreika added a comment - 01/Feb/2017 11:34 AM

Collapse comment: Deleted Account (Inactive) added a comment - 01/Feb/2017 10:56 AM

Expand comment: Deleted Account (Inactive) added a comment - 01/Feb/2017 10:56 AM

Collapse comment: AlanR added a comment - 20/Jan/2017 11:16 AM

Expand comment: AlanR added a comment - 20/Jan/2017 11:16 AM

People

Dates

Backbone Issue Sync