Security improvements, check documentation for more information.

Security improvements, check documentation for more information.

* Compatibility with Jira 8.12 (Support of AUI 9.0)

* Compatibility with Jira 8.12 (Support AUI 9.0)

Security improvements

Security improvements

• CL-358 : Select List - Removing the default option makes the panel inaccessible
• CL-327 : Current date not selectable in a date picker attribute
• CL-330 : Incorrect Markdown link

• CL-358 : Select List - Removing the default option makes the panel inaccessible
• CL-327 : Current date not selectable in a date picker attribute
• CL-330 : Incorrect Markdown link

In this version, we fixed the following issue:

• CL-356 - Deleting a Number Attribute Throw Error "Unable to reload the panel: Cannot read property formatting of undefined"

CL-356 - Deleting a Number Attribute Throw Error "Unable to reload the panel: Cannot read property formatting of undefined"

New security cloud requirements implemented

New security cloud requirements implemented

In this version, we fixed the following issues:

• CL-329 - Glitch when reloading issue ("Unable to create the element: JIRA is not defined")
• CL-326 - New "History" panel is broken with calculate field with custom fields
• CL-322 - Improve the way an issue is reloaded after a Checklist edition

In this version, we fixed the following issues:

• CL-329 - Glitch when reloading issue ("Unable to create the element: JIRA is not defined")
• CL-326 - New "History" panel is broken with calculate field with custom fields
• CL-322 - Improve the way an issue is reloaded after a Checklist edition

This version includes an issue change history with author and date details to help you track changes made.

Here's a full list of improvements:

• Keep track of the changes made to your Checklists in Jira issues - CL-3
• Save author and date of creation or modification of panel configuration - CL-319
• Deactivate list values without impacting existing Checklist panels - CL-282

Fixes

• Error when saving panel on JSD Cloud

This version includes an issue change history with author and date details to help you track changes made.

Here's a full list of improvements:

• Keep track of the changes made to your Checklists in Jira issues - CL-3
• Save author and date of creation or modification of panel configuration - CL-319
• Deactivate list values without impacting existing Checklist panels - CL-282

Fixes

• Error when saving panel on JSD Cloud

Error when calculating footer for lucene index

Error when calculating footer for lucene index

Datacenter compatibility & GDPR compliance

GDPR compliance

Valiantys Software has a new name: Elements, a Valiantys company! We've also renamed our products to provide consistency and clarity across our apps portfolio.

Elements will now be called Elements Checklist.

In this release we made Elements compatible with Jira 8

In this release, we added the possibility to configure the number of decimals that will be displayed in a "calculation" attribute.

• ELT-273 - Be able to specify the number of decimals (Mantissa).

Elements "datasets" have been improved and will now be called "templates" for the sake of clarity.

New feature: we have made it possible to apply all templates matching the issue context to your checklist instead of only activating the first one matching your JQL condition - ELT-149

Bug fix: we have fixed a bug fix in the Java API - ELT-271

ELT-254 - Issue can't be indexed if it contains an Elements panel where a 'Calculated' attribute references a 'Select' attribute

ELT-263 - Groovy script unable to retrieve calculated values when if a condition is defined on a single select attribute

• Issue attribute breaks the Elements panel in Issue view (Cloud version only)
• JQL tester does not work for issue attribute on Jira Cloud
• Auto populate Elements from Dataset does not work if a mandatory field is empty
• Panel does not fit window size in Elements configuration (Jira Server 7.10)

This version brings two new features, along with bug fixes (ELT-185, ELT-187, ELT-167 and ELT-188) and improvements of the german translation:

• choose how numbers are formatted in the issue display
• when you have multiple panels in the same issue, you can now collapse them to focus on the one you're interested in.

Thank you all for sharing your feedback, please feel free to contact us to ask for a feature you miss.

In Elements 1.9 we are glad to announce we've shipped several UX improvements. You can now:

• Edit fields directly from an Elements table, without using a form thanks to the new inline edit- ELT-133
• Reorder items in your table from the issue view - ELT-76
• Select dates with a date picker - ELT-29

Here are the new features available provided by Elements 1.9:

• Search on Select attribute - ELT-156
• Apply user preferences when formatting dates - ELT-30

Performances have been improved and loaders are available to enhance the user experience - ELT-155

Also, "gute Nachrichten für Deutschsprachige" : Elements has been translated to German - ELT-154

This version fixes a bug introduced in Elements 1.8.0, which made panel updates not visible immediately

This version brings a Java API to apps developers or script writers who want to read & write Elements panels.

Read our documentation for more details

Brings a fix for ELT-148

This version fixes a bug:

• Elements panels not visible in the Agile boards

In Elements 1.7 we are thrilled to announce you can now:

• Reference issues in your Elements tables - The project admin can configure a JQL filter to only suggest relevant entries - ELT-140
• Use Markdown to add formatting to your texts and highlight important information - ELT-135

We've also worked on some UX improvements allowing you to:

• Add color to your Select attribute options - ELT-138
• Customize checkboxes headers - ELT-139

Fix a bug introduced in Elements 1.6.1 where empty panels could not be edited.

Go further with Elements templates

• Create multiple templates - configure activation condition based on the issue status - ELT-101 & ELT-118
• Auto-populate a panel with Elements items from a template when an issue is created - ELT-117

We've fixed bugs and improve the storage capacity of the product

• This version fixes a bug which occurred when the visibility of the Attachment field was set to Hide - ELT-121
• When a date attribute was left empty, it was set to 1970/1/1, that's not the case anymore - ELT-109
• We have increased the storage capacity of Elements panel - now you can store twice more items in Elements panels.

Warning

Downgrade to 1.5 is not possible once a project or an issue is edited.

New calculation mode

Let Elements crunch numbers for you and display the results right in your Jira issues with our new advanced calculation features.

Now Jira admins and project admins can:

• Reference number custom fields and any Elements attributes in their formulas (see ELT-89)
• Use condition in formulas thanks to a powerful language similar to JavaScript (see ELT-82, ELT-83 & ELT-84)

Want to see this in action?

See our tutorial and learn how to track expense reports with multiple currencies with Elements.

Other features

We've also improved the user experience! Here's what's new and noteworthy in Elements:

• Non editable & empty panels are not displayed in issue views (see ELT-92)
• URLs entered in text attributes automatically become active links (see ELT-91)
• Two new conditions are available in the JQL search: percentage and number of checkboxes checked / unchecked (see ELT-87 & ELT-85)

If you have any feedback on Elements, our team would love to hear from you!

Release details

This version includes new JQL functions (for Jira server only):

• Retrieve all issues, including panels that either have data or are empty
• Filter issues based on the sum, average, minimum or maximum value of the number attribute

We’ve also fixed bugs:

• Users without "Administrator permission" can now see an elements panel if a role restriction is set
• JQL search on the calculation attribute now works if wrapping other attributes with double quotes
• Role permission now allows editing of the Elements panel if the user is in a group that is granted the proper permission

Due to limitations in the Jira Cloud API, we had to remove the ability to set editing permissions based on the role of the current user. We apologize for the inconvenience and remain available should you have further problems.

Our next version is scheduled for end of year and will bring the calculation attribute to another level - so stay tuned!

This new 1.3.0 version embeds new functionalities that will undoubtedly make the creation and edition of your tasks easier than ever!

• Panel templates : pre-fill the panels with repetitive information so users gain time.
• Move panels as needed : insert a panel where you want on the Elements panel or move it around so it's exactly where you want it to be.
• New attribute : version is now available. List all versions of a project. We now offer 10 different attribute types
• Edition restriction : users can modify panel content only if they are set in a specific User field.

Discover the full release note here

Project admins can add edit permissions on their Elements panels, based on:

• issue status (i.e.: Expense reports can only be edited when in the "Submit expense" status)
• user role (i.e.: Only developers can edit development tasks)

A "copy element" button has been added to the issue view - no more copy / paste between Elements

Read the full release note.

We are already working on the next version, it will be released shortly.

Do not hesitate to share your thoughts about Elements, send us an email at addons@valiantys.com.

A key feature is missing? please, ask for it!

• New attribute types: "Select list" (ELT-5) and "Component" (ELT-16)
• Project administrator can set the default value of an attribute (ELT-17)

Next version is already under development, it will be released in two weeks: stay tuned for new features!

We developed Elements with the user and project admin in mind, making it the ideal solution for expense reports, assets ordering, dev estimate calculation, training registration tracking and more.

We developed Elements with the user and project admin in mind, making it the ideal solution for expense reports, assets ordering, dev estimate calculation, training registration tracking and more.

Creating subtasks requires a Jira admin - which isn't the best use of their time. The UX is clunky as users have to go through multiple panels to create one sub-task. If you need to add numerous, structured items within an issue, these sub-tasks can impact your instance's performance.