Hi, I recently found some problems in my JIRA Project Backlog :
1. some task that were set to Done, they cannot appear. (I've checked the filter, no filter out the DONE task). Anyway to fix this?
2. another project (Project A) Sprint were moved to current project (Project B), is that due to moving the task from Project A -> B? how can it to be removed?
For (1) - this is by design if your "Done" statuses are in the last column of your board - see here for detail on how and why.
You could reverse the detail in the link above to make Done issues appear if you wish - by not having "Done" in the last column of your sprint board.
But I would advise considering if you need to see "Done" issues in your backlog - which is usually used to visualise upcoming work or work in a sprint, rather than completed work which you could visualise separately in a dashboard or issue filter.
For (2) - are you seeing issues from Project A in Project B? Or you're seeing Project A issues in Project B's sprint?
If in the project, these would have been moved here - you'll need to move them back.
If they're in your sprint - they would have been added there also. Check if the sprints have different names - otherwise users might be putting the wrong sprint into the "Sprint" box :)
Not sure if this resolves (2) - if not, give us some more info so we can help further.
thanks for your reply.
For (2), I previously moved some tasks within a Sprint (e.g. Sprint SepA) from Project A to Project B, by default I saw JIRA also copied the Sprint Name to Project B...
I didn't realised that the copied Sprint (Sprint SepA) is still linking to Project A..., I guess it should be just a copy and separated from Project A...
So I move those tasks to my other Sprint in Project B, and tried to modify/delete the Sprint name (Sprint SepA) in Project B, but it affects in Project A...
So just to confirm:
Can you tell me what impact it has on Project A?
Some clarification on how sprints and boards work which might be useful:
Applied to your circumstances - this means that Sprint A hasn't moved to Project B - it remains active and issues that were in it still are, regardless of what Project they're now under.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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