LYNX

New update, action required

We at A-dato are excited to introduce a crucial update for LYNX packed with significant enhancements.

This update is mandatory, but you can do it at any time.

While this update is essential to access the latest features and ensure compatibility with our new system infrastructure, please be assured that your current version of LYNX will continue to function. We understand this update process may differ from what you're accustomed to, but transitioning to the new version is critical for seamless future operations as the previous version of LYNX will no longer be automatically updated.

How to Update:

1. Uninstall the Previous Version: Navigate to 'Add or Remove Programs' in Windows, find the old LYNX version, and select 'Uninstall' to avoid any confusion.
2. Download the New LYNX: Download the new app installer using this link: https://lynx.a-dato.com/lynx/lynx.a-dato.appinstaller.
3. Install the New Version: Run the app installer to install the updated LYNX on your system.

We're Here to Help:

If you encounter any issues or have questions, reach out immediately at support@a-dato.zendesk.com. Our support team is ready to assist you through this update process.

What's New?

Our latest update builds on our solid foundation, enhancing LYNX with new technologies and incorporating feedback from users. We've migrated to a new server and we have an updated environment to offer you:

• Optimized Performance: Quicker, more reliable project management tools.
• Improved Usability: New features, enhanced critical chain functionality, and a more stable environment.
• Enhanced Integration: New features that enhance compatibility with Jira, streamlining your workflow and improving efficiency.

 

Revised Critical Chain (CC) Behavior

New behavior of the critical chain is implemented. The old behavior was LYNX selecting the critical chain via following the tasks with the highest amount of work. Now, the critical chain is created via following tasks with the longest project duration, taken into account the working hours. 

The benefits of the new behavior include:

• Reduction in the number of tasks being part of the Critical Chain, allowing more focus.
• Communication of Critical Tasks with (most) reduced availability of resources to management.
• Allows for better resource allocation, and easier identification of bottlenecks in resources.

Example:

Old (4 tasks): Critical Chain follows the tasks with the highest amount of work

New (3 tasks):” Critical Chain follows the tasks with the longest project duration

 

Revision of definition of non-working hours

Non-working days are calculated and added to the Critical Chain/Current Chain (released) as follows:

• If a person works part-time 4 days a week: 1 non-working day is added (per week).
• If a person is working at 50 % (4 hours per day): 2,5 (20h) non-working days are added (per week)
• If a person is absent due to vacation or training: the number of absence days are added to the non-working days

Jira Integration Improvements

Before the upgrade, project managers had to set up and connect workpackages in LYNX with those in Jira. They also needed to pre-define all the workpackages relevant for their project.

The new Jira integration features in LYNX now simplifies  this process, allowing for the automatic matching of cards to their corresponding workpackages based on predefined properties. Card and task custom fields in LYNX now match up with card properties in Jira, enabling seamless synchronization of task attributes like customer numbers or components. The new linking of cards (subtasks) in LYNX to the correct Workpackage task is directed by shared properties in both systems. This ensures tasks are organized under the appropriate project "workpackages" (task type) without human interference.

This enhancement is advantageous for JIRA users as it allows them to specify task properties without needing to determine the workpackage assignments, streamlining the workflow. For project managers, it removes the need to arrange workpackages beforehand in the planning phase, leading to a more efficient project initiation and management process. It also enables them to identify if new workpackages are necessary for the imported cards, and quickly associate those new cards to the workpackages.

An example of task custom fields and cards custom fields which match properties in Jira:

Furthermore, the integration now offers advanced import options, enabling users to employ JQL (Jira Query Language) for selective card imports into LYNX. This feature optimizes project setup and ensures precise synchronization between the two platforms, enhancing the project management experience to cater to specific project requirements and structures. The use of JQL permits project managers to import only relevant JIRA tasks, thus avoiding the accumulation of unnecessary cards and reducing the need for additional organizational tasks.

Explanation: In the card view in LYNX, when you use the "Synchronize" button, you now have the option to use JQL query to filter which tasks you are updating. You need to use the checkbox to "update to a workpackage with corresponding tasks" to match the cards with the correct workpackage. 

 

Fixes/Improvements:

• In the fever chart, the absolute minimum was set to -50%. This is now removed so the tag is always showing.
• Updating tasks within "My Activities" tab and "Active Tasks" tab no longer jumps to another position. You need to refresh and you will see an orange circle by the refresh button to show that a refresh is needed.
• Reporting fixes:
  • You can now close a report when you have multiple open without an issue.
  • In raw: tasks table, there are two new fields EarliestStartPosition and EarliestStopPosition.
  • Task: Overview report used to give an error.
  • Raw: cardhistoryitems table used to give an error.
  • SQL table structure.html document used to give an error.
• In the German version of LYNX, you can now choose different relations in dependencies without issues.
• The wrong chain length was taken when creating buffers in some project which is now fixed.
• The feeding chain in some projects was not detected correctly causing a lot of negative progress, this is now fixed. 
• Some improvements in visualization.

 

LYNX-X

There are many changes and improvements implemented and more are coming soon to LYNX-X! 

This application is still in development, so please let us know if you find any issues on: support@a-dato.zendesk.com