How to Collect Logs
Frequently Asked Questions for EasySync
What fields does EasySync Support?
| Fields | Supported? |
|---|---|
| Labels (built in) |  |
| Teams (built in) | |
| Label type custom field | |
| Team type custom field | |
| Tempo Account | |
Can the same field be used in multiple rules?
No, a field can only by listed on one rule at a time. This is to avoid possible scenarios where two different rules try to update a field to different values.
What is the JQL Stop condition?
If an issue issue matches the JQL Stop Condition processing will stop - The matching issue and it's children will not be updated.
Can I use Project Categories instead of a list of projects?
Yes, project categories can now be used. When using project categories, projects from within those categories can also be excluded.
Are cross project hierarchies supported?
Yes, for example if your Initiative is in a project "Programme management", and Epics are in delivery projects, as long as both projects are in the rule configuration, field values will be synced across projects.
My Project has been Archived or Deleted, do I need to do anything?
No, in release 3 we have resolved this issue, so now no action is required.
I made a change and the children's field is not updating.
This could be for a number of reasons:
- Ensure the rule is configured correctly
- The issue is in the listed projects, or project categories and has not been excluded.
- The JQL Stop condition does not match the any of the parents, grand parents, etc up until the issue pushing the change down.
- There is a delay for actions affecting large number of issues, for example bulk issue editing or saving an Advanced Roadmap plan. Propagation may take several minutes.
- Large hierarchies. The larger the tree the more searching and editing EasySync needs to do. Propagation may take several minutes.
- If you are viewing a child issue during a propagation you may need to refresh the page to view the new field value.
Do fields need to be on an issue type screen?
No. Issues without the field on any screen will still have the field's value propagated to it and it's children.
Do the fields need to be on an edit or create screen?
No. Issues without the field on the edit or create screen for an issue type will still be propagated to it and it's children.
Do fields need to be on an issue type?
No. If a field is not in the context of an issue type,, the field will still be propagated to it's children.
Does EasySync work with Team Managed Projects?
Yes.
Does EasySync work with Company Managed Projects?
Yes.
The field I want to sync is not supported.
Please contact us – we would love to hear about your use case.