---
title: "Auto-indexing"
canonical: "https://support.appfire.com/space/JMCF/465437049/Auto-indexing"
format: markdown
---
> Macro (aura-html)

# Manage auto indexing rules

**Which issue(s)**

Select the issues to operate on. They can be:

- **Parent issue of the current sub-task:** Select this option to operate on the parent of the current issue
- **Sub-tasks of the current issue: **Select this option to operate on the sub-tasks of the current issue
- **Epic of the current issue: **Select this option to operate on the Epic of the current issue
- **Issues that belong to the current Epic:** Select this option to operate on the issues that belong to the current Epic
- **Parent issue of the current issue in the Portfolio hierarchy:** Select this option to operate on the parent issue of the current issue in the Portfolio hierarchy
- **Child issues of the current issue in the Portfolio hierarchy:** Select this option to operate on the child issues of the current issue in the Portfolio hierarchy
- **Issues linked to the current issue through any link type**: Select this option to operate on all issues linked to the current issue
- **Issues linked to the current issue through the following link type**: Select this option and select the link type to operate only on issues linked through a specific link type
- **Issues returned by a Groovy script: ** Input a Groovy script that returns either a single [Issue object](https://appfire.atlassian.net/wiki/x/zASrB), or a Collection of [Issue objects](https://appfire.atlassian.net/wiki/x/zASrB), or a String representing the key of an issue, or a Collection of Strings each representing an issue key. For example:
  - `"TEST-1"`
  - `["TEST-1","TEST-2"]`
  - `ComponentAccessor.issueManager.getIssueObject("TEST-1")`
  - `[ComponentAccessor.issueManager.getIssueObject("TEST-1"),ComponentAccessor.issueManager.getIssueObject("TEST-2")]`
  - `issue.parentObject`
  - `issue.getLinkedIssues()`

# Use case

Consider a case where you have a Calculated Multi-user field that displays the assignee of the subtasks of the Story. The calculated custom field script will be: 

```
issue.subtasks*.assignee - null
```

If you change the “Assignee” of one of the subtasks and do not reindex the Story or edit the Story, then when you use the Issue navigator search with the Calculated Multi-user field the search will not display the right results since the Story has not been reindexed. To work around this add an auto-indexing rule to reindex the Story when the subtasks are modified.

1. Go to JMCF administration pages
2. Click on Automatic Indexing
3. Click on “Add auto-indexing rule”
4. Select the Issue Link as “Parent of the current issue”
5. Click on “Save”

---