Ollie Guan Community Champion

An issue will only be visible in Plan mode if:the issue matches the board's Saved Filter (see Configuring Filters); andthe issue's status maps to one of the board's columns (but not the 'Done' column).

what is the issue status?

First of all, according to the concept of the sprint, a story should be done in a sprint, then his child tasks should also end in a sprint. If child tasks not completed, so the story of his superiors should also partially completed. When you complete Sprint,you can remove the Story from the sprint, this story will continue…

My team have encountered a similar situation Suggest administrator rebuild index REDEX.jpg

Only the Filter/Kanban Owner can Edit the saved Filter KANBAN.jpg

Why don't you add a Column of Resolved, Match the Resolved state to the column? 

Through the workflow configuration should be able to achieve Post Function:Transition parent when all subtasks are resolved--This will do the given action on the parent when all sub-tasks are resolved https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner

https://confluence.atlassian.com/display/AOD/Associating+a+Screen+with+an+Issue+Operation

Configure Screen Scheme https://confluence.atlassian.com/display/JIRA051/Defining+a+Screen

Confirm these sub-tasks sprint id is the only? Associated with the sprint id of 2 or more? Ever try to rebuild indexes?

How do you write this filter of the query? 

JQL: issueFunction not in linkedIssuesOf("", "") issueFunction not in hasLinks("") https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions

First of all, please check your Agile Board columns and subtasks status matching set Only Done column matching Status are considered finished subtasks Second, you can use the following query unfinished subtasks For example:sprint in openSprints() and project = XXX and status != closed

Add special labels to this kind of Issue Then Edit the kanban Filter likes project = XXX and labels != xxx

When you create, see if there is a default value? Suggest to check the workflow of Create issue post function, whether some action empty the default value

Whether to set default values for it in Configure Custom Field？ default.jpg

To Re-estimate or not https://answers.atlassian.com/questions/125910/sprint-report-completed-story-points-figures-not-taking-into-consideration-updates-to-story-point http://www.mountaingoatsoftware.com/blog/to-re-estimate-or-not-that-is-the-question 1234.jpg

in sprint report https://confluence.atlassian.com/display/GH061/Viewing+the+Sprint+Report

Please check your workflow Settings Post Function-->Re-index an issue to keep indexes in sync with the database. Assign the issue to the XXX condition Should Before Re-index

I met the same problem

This depends on whether you have the permission of the Assignee Issue Permissions Explanation Assign Issues Permission to assign issues to users. (See also Assignable User permission below) https://confluence.atlassian.com/display/JIRA051/__project+permissions

It's better to deactivate the user than deleting.https://confluence.atlassian.com/display/JIRA/Managing+Users#ManagingUsers-Deactivatingauser

If you don't use Assignee to me Gadger.but using the Filter Results Gadget(Assignee = currentUser) can it be solved? or try to use the problem user account, Use JQL query: Assignee = currentUser () and resolution = Unresolved whether can find out the data? 

Or don't use the default IssueType = Bug, custom class of Sub - the tasks issue like Sub - bugs, create Sub - Bug under the Story, this Sub - bugs will automatically inherit the Story sprint id Then You can use the following query Sprint = XXXX and issuetype = sub - bugs

Base Swimlanes on Queries JQL： * Story Issuetype =Story * David Assignee= Daved * Peter Assignee =Peter * Lily Assignee =Lily * ......

Try the plug-in Color Custom Field https://marketplace.atlassian.com/plugins/ru.mail.jira.plugins.color-custom-field-plugin https://marketplace.atlassian.com/plugins/ru.andreymarkelov.atlas.plugins.colorfields

Pls check the notification Events---Work Logged On Issue

I think Agile Board rule is created with the filter, rather than with the project Although the data query device detected belongs to a project, but the data filter, find out the condition of two queries data without any commonality, so not visible to each other

Hi Denise, I tried the gadget“ filter results ”, it can be sorted by JQL specified statement What is your JQL? 

you can try this plugin https://marketplace.atlassian.com/plugins/at.celix.jira.plugins.column-order