Configuration - Administrators Guide
- Hachim Khaldi
Analytics
Welcome to the Chronova Administrator's Guide. This guide covers key administrative tasks to help you manage Chronova effectively, including:
Accessing the Admin Section
After installing Chronova in Jira, you can access the admin section in two ways:
Via the Jira Sidebar: Locate the Chronova app icon in the Jira sidebar and click on it to navigate directly to the admin section.
Through Manage Apps: Go to Jira Settings in the main menu, select Manage Apps, find Chronova in the list of installed apps, and click on Configure to access the admin section.
Associate field budget to screens
Your first step in the budgeting journey will start with enabling our custom field, it comes pre installed with the app so you just need to enable it from the Jira interface.
Use the Jira sidebar or navigate to Manage Apps > Chronova > Configure
Click on Configure in Jira, that will redirect you to Jira interface so you can check the screens where you want to add budgets.
Managing Roles
Roles in Chronova are essential for overseeing team members' responsibilities, particularly regarding contracts and workload distribution. The primary purpose of role management in Chronova is to manage user contracts by clearly defining the responsibilities and contributions of each member within a project.
Default Roles
Chronova includes the following predefined roles: System Administrator, Software Developer, Project Manager, IT Support Specialist.
Creating Custom Roles
If the predefined roles do not fully meet your organization's requirements, Chronova allows you to create custom roles tailored to your specific needs. Custom roles assist in managing contracts by aligning roles with contractual agreements and ensuring that team members are appropriately categorized based on their responsibilities.
To create a custom role:
Access the Admin Section
Use the Jira sidebar or navigate to Manage Apps > Chronova > Configure.Navigate to Roles
In the admin section, select Roles.Create Role
Click on Create Role.Enter Role Details
Provide the Role Name, a Description, and set a Default Rate.Save the Role
Click Save to make the new role available for assignment.
Managing Expense Categories
Efficient expense management is crucial for keeping projects within budget. Chronova allows administrators to categorize expenses and monitor them across various projects, facilitating better financial oversight and reporting.
Expense Categories
Organizing expenses into categories enhances clarity and simplifies reporting. Common categories include Travel, Supplies, and Consulting Fees.
To create a new category:
Access the Admin Section
Use the Jira sidebar or navigate to Manage Apps > Chronova > Configure.Navigate to Expense Categories
In the admin section, select Expense Categories.Add Category
Click on Add Category.Enter Category Details
Provide the Category Name and an optional Description.Save the Category
Click Save to add the category.
You can also edit or delete existing categories as needed to maintain accurate financial tracking.
Managing Time Tracking Providers
Chronova integrates with time tracking tools that have already been configured in your Jira instance. You cannot add new providers directly from this section; it is used to display the current status of enabled time tracking providers and configure existing ones like Tempo.
For more details on how time tracking works in Chronova, please refer to the Time tracking providers .
Supported Providers
Chronova currently supports integration with the following providers:
Jira Provided Time Tracking: This is the default time tracking system enabled in Jira.
Tempo Timesheets: Requires additional configuration via an API token.
Accessing Providers
Access the Admin Section
Use the Jira sidebar or navigate to Manage Apps > Chronova > Configure.Navigate to Providers
In the admin section, select Providers.Configure Providers
You will see the status of enabled providers like Jira or Tempo. For providers like Tempo, additional configuration such as entering an API token is required.
How to Obtain the Tempo API Token
Log in to your Tempo account.
Navigate to the API Access page (usually found under the Account or Settings section).
Generate a new API token by following the provided instructions on the API Access page.
Paste the generated token into the token field displayed in the Chronova admin section.
The API token is essential for authenticating requests to the Tempo API and has an expiration date, which you should monitor to avoid interruptions in the integration. Ensure that the token has the necessary admin rights to view other users' worklogs, as insufficient permissions can result in errors when accessing time tracking data.
For more details, refer to the Tempo API documentation.
Important Note
The actual enabling and switching of time tracking providers (Jira or Tempo) must be done by an administrator in the Jira global settings. This section is only for viewing the status and configuring providers like Tempo that require an API token.
Now your time tracking provider is setup in Chronova.
To ensure full visibility of worklogs of a Chronova project, you must have permission to view the worklogs of all project members. Without this permission, you will not be able to view or track their worklogs.
Reviewing Project Logs
Project Logs in Chronova provide a comprehensive audit trail of all activities across all projects within your Jira instance. This feature is invaluable for tracking changes, identifying issues, and maintaining accountability.
Accessing Project Logs
To access logs for all projects:
Access the Admin Section
Use the Jira sidebar or navigate to Manage Apps > Chronova > Configure.Navigate to Logs
In the admin section, select Logs.View Logs
You can view detailed logs related to all projects, including expenses, worklogs, and other activities. The logs are displayed in chronological order, showing the user who performed the action, the module affected, and additional details.
Understanding Log Entries
Each log entry includes the following:
Timestamp: The exact time when the action took place.
User: The user who performed the action.
Action Description: A summary of what was done (e.g., added a worklog, modified an expense).
Affected Module: The part of the project that was affected (e.g., Expenses, Worklogs).
Additional Details: Any relevant details that provide more context about the action.
Using Logs for Auditing
Project Logs are essential for:
Auditing purposes: Ensuring compliance with organizational policies.
Troubleshooting: Pinpointing when and where an issue occurred.
Performance Analysis: Analyzing team performance and productivity over time.
Troubleshooting
If you encounter issues while managing Chronova, here are some common troubleshooting steps:
API Token Errors: If your Tempo API token has expired or lacks necessary permissions, regenerate the token and ensure it has full admin rights to view worklogs.
Permission Denied: Ensure the role assigned to the user has the proper permissions to access the relevant sections, such as project logs or provider settings.
Time Tracking Provider Not Syncing: Verify that the enabled provider (e.g., Tempo) is correctly configured and that the API token is valid and has not expired.
Missing Logs: If project logs are not displaying correctly, check the user’s permissions and ensure that the log settings are correctly configured.
By effectively managing roles, expense categories, time tracking providers, and project logs across all projects, administrators can optimize Chronova to meet their organization's needs. These tools ensure controlled access, accurate financial tracking, seamless integrations, and thorough auditing, all contributing to successful project management and enhanced team collaboration.
For further assistance or advanced configurations, please refer to the Chronova Support Center or contact our support team.