...
...
...
...
...
...
...
...
...
...
...
...
...
In case the system is not connected to any Jira fields (No field selected), the system will store the information about Start/End dates internally without synchronizing it with Jira. However, we do recommend configuring this type of integration as it’ll allow to use ActivityTimeline in the most effective way.
When you change the configuration of the fields, you need to perform a synchronization of issues with Jira, so that the system could re-cache issues with proper dates.
To do this go to Synchronization→Refresh issues→Perform full synchronization, so that system could re-cache all the issues.
...
Note:If you already have some issues scheduled on your dashboard, changing the configuration of your Start/End Dates field, will remove them from the schedule, so we recommend firstly make sure that all those tickets also have Start/End dates set in Jira.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Important:You can use the following fields to integrate ActivityTimeline with other applications that use date picker fields, like BigGantt or BigPicture by Softwareplant. You can check our guide on how to perform this integration here. |
Check the video example here: Video Example: How to map Start/End dates from Jira to ActivityTimeline?
If you have any additional questions related to the following section, please don’t hesitate to contact our team at: support@reliex.com.
Frequently Asked Question. Read more.
📰 Helpful tips in our Blog.
📬 Questions? Contacts Us.
🤝 Contact details for Solution partners.
Search doсumentation
| Live Search | ||||
|---|---|---|---|---|
|