Versions Compared

Old Version 1

changes.mady.by.user Ostap Zaishlyi

Saved on

compared with

New Version Current

changes.mady.by.user Svitlana Samotis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In Advanced Settings ActivityTimeline administrator can set a system notification message, if he wants to communicate some information to ActivityTimeline users (i.e. Maintenance time on the server), change

...

  • Default Date Format

    • Specifies Date format. Should be the same as for Jira Date Picker field. 

    • Default Value: d/MMM/y

  • Default Date/Time Format

    • Specifies DateTime format. Should be the same as for Jira DateTime Picker field. 

    • Default Value: dd/MMM/yy h:mm a

  • Timezone shift/fix

    • Defines Time Zone shift in hours. Please change this value if tasks appears shifted by one day on the dashboard. If you use Date/Time format and you see that there is a discrepancy between Jira and ActivityTimeline you can also utilize this feature, however it is recommended to contact our support team for such cases.

    • Possible values:

      • negative value - move tasks few hours back;

      • positive value - move tasks few hours forward;

      • 0 value - no time zone shift.

    • Default Value: 11.5

Other

...

Custom Functionality

  • Turn On or Off features that are currently not turned on by default.

    • Set value to 1, 2, 3 or combination of them to enable custom ActivityTimeline features.

  • Default Value: 0

limits for the synchronization process, and apply some custom functionality.

  • Reuse Jira Project permissions for each User

    • Defines whether ActivityTimeline should reuse Jira Project Permissions in addition to built-in ActivityTimeline User roles. The system will reuse Jira Project Permissions for each logged-in user if enabled.

...

    • Possible values:

      • unchecked - default ActivityTimeline User Roles are used to filter issues/teams

      • checked - Jira Project Permissions and ActivityTimeline User Roles are enabled to filter issues/projects/teams

    • Default value: unchecked

  • Reuse Jira permissions per Issue (slow)

    • Defines whether ActivityTimeline should reuse Jira Issue Permissions in addition to built-in ActivityTimeline User roles. The system will reuse Jira Issue Permissions for each logged in user if enabled

...

    • .

    • Possible values:

      • unchecked - default ActivityTimeline User Roles are used to filter issues/teams

      • checked - Jira Issue Permissions and ActivityTimeline User Roles are enabled to filter issues/projects/teams

    • Default value: unchecked

...

Auto add/remove users to/from Project Team based on assigned events

...

System will automatically add users to project team (if created) when new Booking event gets assigned to him/her.

...

Note

Enabling these settings provides more granular control over what users can see based on their Jira permissions. However, enabling the “Reuse Jira Permissions per Issue” setting may lead to a decrease in dashboard performance due to the additional checks required.

  • Decimal Delimiter Symbol

    • Different languages have different delimiter symbols in numbers.

      It is required to correctly set it so that Jira can understand the value of the estimate or worklog hours.

      English & Chinese: choose Decimal Point; German, Russian, Spanish, French & Italian: choose Decimal Comma.

    • Default Value: Decimal Point

  • Custom Functionality

    • Turn On or Off features that are currently not turned on by default.

      • Set the value to 1, 2, 3, or a combination of them to enable custom ActivityTimeline features. Custom Functionality is provided by the Support Team upon request if necessary to resolve the use case.

    • Default Value: 0

  • Number of Issues to Load from Jira

    • Defines the maximum amount of tasks that ActivityTimeline should retrieve from Jira during Setup Wizard Synchronization

    • Recommended maximum: 100000

    • Default Value: 10000

  • Number of Worklogs to load from Jira

    • Defines the maximum number of worklogs that ActivityTimeline synchronizes from Jira.

    • Recommended maximum: 100000

    • Default Value: 

...

    • 10000

  • Ignore issues older than (NN months)

    • Do not synchronize issues, which were last modified more than NN months ago. 

    • Default Value: 

...

    • 18

  • Amount of Issues to load per request

    • Defines the amount of issues to load per each request to the server.

    • Default Value: 

...

    • 1000

  • Issue ID in Jira

    • System property. Should not be changed manually.

    • Default Value: 1001

  • Unresolved Resolution ID

    • Defines an extra resolution status id. Jira tasks with this ID will appear in left issues panel in addition to all unresolved tasks.

    • Default Value: [EMPTY]

If you just started trial and find some issues missing in ActivityTimeline, you may need to increase the limits ‘Number of Issues/ Worklogs to Load from Jira’. For more detailed info, please, refer to:

https://activitytimeline.atlassian.net/wiki/spaces/AC/pages/1592885267/Customer+Q+A+-+PLAN.+Issue+Panel+Filters#I-started-a-trial-and-cannot-find-some-issues-in-ActivityTimeline

If you have any additional questions related to the following section, please don’t hesitate to contact our team at: support@reliex.com.

Also, you can check our Quick Start Guide to get started with ActivityTimeline in under 5 minutes.

(question) Frequently Asked Question. Read more.

📰 Helpful tips in our Blog.

📬 Questions? Contacts Us.

🤝 Contact details for Solution partners.

Search doсumentation

Live Search
spaceKeyAC
placeholderSearch doсumentation...