Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated by Automated release notes for Jira
 Image RemovedImage Added 

...

10/Jul/18

Updates:

3.8.3

9th April 2022

09-Apr-2022 

Stories (

...

3)

Ability to connect Jira issues to KRs as Actions 🎁

Acceptance Criteria

  • We've recently released advanced OKR settings for 'Progress calculation of Jira issues as KRs'
  • Enhance this section, name it - Key result configurations
    • Enable key results - checkbox (default true - new install as well as upgrades)
      • Metrics - disabled checkbox (always true)
        • Link Jira issues as actions - checkbox (default true - new installs as well as upgrades)
      • To Do - disabled checkbox (always true)
        • Link Jira issues as actions - checkbox (default true - new installs as well as upgrades)
      • Jira Issues - checkbox (default true for upgrades, default false for new installs)
        • If the above is checked, today's progress calculation for jira issues as KRs checkboxes will be available else hidden
  • Impact of checkboxes
    • When KRs are enabled system will work as it does today
      • When KRs are disabled, don't display 'Add key result' action anywhere.
      • And if there is no key result to an objective, don't display 'Key Results' section within the objective details page.
    • Whether Jira issues can be linked as Key Results, will depend on the 'Jira issues' checkbox
      • if disabled, don't display Jira issues option when adding a key result
  • Impact of 'Link Jira issues as actions'
    • For metric or to do type of KRs, if the corresponding checkboxes are checked - a new section will appear on KR details page
      • Actions
        • Empty state message - Add Actions - Actions are the initiatives, projects, tasks that are undertaken in order to achieve the key result. Connect Jira issues as actions to gain clarity on how the KRs are achieved.
        • There will be an 'Add New' button clicking on which the Jira issue search pop-up appears.
        • Similar to the existing flow, one or more Jira issues can be linked to the KR as actions.
        • Once added, they will appear in the list with a delete icon.
        • We will not add any logic for maintaining visibility for assignees of those Jira issues.
        • This linkage will not have any bearing on the progress of key result.
  • Impact on history
  • Impact on list view
  • Impact on hierarchy view
  • Impact on UpRaise panel on issue details page
  • Impact on project restrictions
  • Impact of 'disabling key results' needs to be assessed on dashboards/reporting

 

Improvements (6)

Improvements in add alignment pop-up 🎉

‌h3. Acceptance Criteria

  • In the current 'add alignment' pop-up (& search objective in hierarchy view) it is difficult to figure out owner of an objective & its due date - if the title is lengthy.
  • Change this so that
    • on hover entire text is displayed.

User profile & team profile page UI improvements 🎉

‌h3. Acceptance Criteria

  • Refer to attached screenshots & modify the Team profile, user profile pages accordingly
  • Current & Desired screenshots are attached
  • Check with Anand the new user profile layout would look like. In both cases (team & user profile), additional tabs & actions will be visible as they are today.

UpRaise admin/super admin list for Jira admin 🎉

Acceptance Criteria

  • For Jira admins, provide a link under Atlassian Marketplace that says 'UpRaise Admins'.
  • This link & page will be available only after the 'Getting started' process is completed.
  • On this page, Jira admin will be able to view list of all UpRaise administrators & super administrators.
    • Show two buckets - Administrators, Super administrators
  • On each of the buckets, provide an 'add' action that will allow adding a new user to company directory/ updating an existing user in company directory as 'admin' or 'super admin'
    • If the user being added does not already exist in UpRaise company directory - add them to the directory with admin/super admin role.
    • If the user already exists, update their role to 'admin' or 'super admin'.
  • Within the add pop-up, display a warning message 'All current admins & super admins on UpRaise will be notified of this action.'
  • This add pop-up will only have a user selector along with UpRaise role selector. No additional user profile attributes are required.
  • When the user is added, send a mail to all current admins/super admins. get the email template from Anand

UpRaise panel on Jira issue details page, revision due to UD-2349 🎉

‌h3. Acceptance Criteria

  • When an issue is connected with an objective as a key result or with a key result as an action - appropriate details should be displayed on that issue's detail page.
    • This issue is a key result of following objective
    • This issue is an action of following key results

UI/UX improvements for Hierarchy view 🎉

‌h3. Acceptance Criteria

  • Currently when an objective is searched, it appears as the top level node & if children nodes are available - they can be expanded.
    • Modify this so that, parent as well as children nodes for the searched objective are displayed in the hierarchy view.
    • If possible, expand one level above & one level below the searched objective automatically when the search results are displayed.
  • Provide ability to zoom in/zoom out in the hierarchy view.
    • If required we can provide pan/scroll bars
  • Provide way to download the hierarchy view in an image/pdf format.

Add tagging feature for KR description same as objective description 🎉

Add tagging feature for KR description same as objective description

As of now tagging feature is available in application wherever text area is available except conversation, so need to implement tagging against KR description and accordingly shared with section should get updated.

Note: Tagging while adding comment,punch against KR is available

 

Bugs (14)

Issues in action against KRs 🐞

Issues in action against KRs

1. Issue already linked with KR is displayed in console while the checkbox is not checked when adding action against KR
2. Actions against KR are not visible when KRs are rearranged in list view
3. Add key result popup is displayed while editing key results from kr detail page second time
4. Empty popup is displayed when adding KRs from objective detail page consecutively (from second time onwards)
5. KR action are disappeared when kr is edited

Minor enhancement on user/team profile pages 🐞

Minor enhancement on user/team profile pages

1. Update label of team members on users profile page to Direct reports
2. Align company directory link with below labels of the page

Issues while adding users as admin/super admin 🐞

Issues while adding users as admin/super admin

1. Empty message not available hen user clicks on add button in popup and no user is selected
2. When clicked on user drop-down cursor doesn't move to search box opened for typing
3. When non upraise user added to add admin/super admin popup add button doesn't work and note entry of user should be made to email_notification table in this case
4. UpRaise admin link on add on settings page not visible when initial setup is incomplete
5. UpRaise admin list on manager addon page visible only to upraise admin/super admin

Issue in add action against KR 🐞

Issue in add action against KR

  • Action added against metric todo are visible as KRs against objective in list view
  • Null pointer exception while adding metric against objective. ( log2.txtImage Removed Refer attached logs)

Steps:
1. Access browse okr list view page
2. Enable/Disable JIRA issue as KR on OKR setings page in new tab
3. Now on browse OKR page refresh the page using refresh action given with pagination
4. Now try to add KRs and click on next
5. Observe empty popup is displayed
and null pointer exception in backend
6. jira issue added already to objective msg in console when jira issue not added against same

Issue assignee's are not added to shared list of OKR while adding actions against objective 🐞

Issue assignee's are not added to shared list of OKR while adding actions against objective

Steps:
1. Add an objective assigned to user X and shared with to user X only
2. Now add KR against above objective
3. Add actions against KR which are assigned to some users
4. Observe issue assignee's not added to shared list of OKR

Expected : Issue assignee's should get added to shared list of OKR while adding actions against objective same as while adding issue against objective
Actual : Issue assignee's are not added to shared list of OKR while adding actions against objective

Issues in add action against KRs 🐞

Issues in add action against KRs

1. Show more button is not available when actions against KRs are more than 5
2. Add action functionality is not working on team profile page
3. User unable to delete KR actions when linking JIRA actions are disabled
4. Key results are disabled error message is displayed when actions/JIRA issues are disabled
Expected : Appropriate error message should be displayed for actions/JIRA issue disabled

While navigating in add key result popup, popup is changed with content 🐞

While navigating in add key result popup, popup is changed with content

Currently while navigating in add key result popup one popup is hide/displayed when clicking prev/next.

Expected : While navigating in add key result popup content should change and not popup
Actual : While navigating in add key result popup, popup is changed with content

Issues with adding actions against KR 🐞

Issues with adding actions against KR

1. Page needs to be refresh when JIRA issue as KR is disabled and add new KR is clicked
2. Entry in objective history is also made when action against KR is added/deleted
3. Actions count agsint KR is not updated on objective detail page
4. Actions added against KR are not visible in list/thumbnail view of OKR
5. Multiple error messages is displayed when no issue is selected and clicked on next button in popup

Issues in tagging users against KRs 🐞

Issues in tagging users against KRs

1. URL of tagged user is displayed in objective and KR description and in history
2. Tagged user not added to sharing when KRs are edited and appropriate message that user will be added to sharing also not displayed
3. Drop down after tagging on user is not closed
4. Sharing message is also available when objective is shared with all users while adding KRs
5. Tagged user key is displayed in exported excel for OKRs

Error message is not displayed when changing objective sharing and only JIRA issue is linked 🐞

Error message is not displayed when changing objective sharing and only JIRA issue is linked

Steps:
1. Add an objective for user X (shared with is set to all users)
2. Add KR JIRA issue against above objective which is assigned to user Y
3. Now from detail page update sharing of objective from all users to none by clicking + icon
4. Observe no error message displayed
5. Now add metric/to do against objective and try to change visibility to none
6. Observe error message is displayed

Expected : Error message should be displayed for sharing objective with atleast one user who owns at least one of direct key results (which can be only jira issue, only todo/only metric, combination of KRs)

Actual : Error message is not displayed when changing objective sharing and only JIRA issue is linked

Issues in navigating user profile from company directory page 🐞

Issues in navigating user profile from company directory page

1. After clicking any of the user available in list of company directory ''viewing 11 of X'' is displayed though 5th,10th user in list is clicked

2. After performing above step click on forward arrow until page 1st user list is over against viewing x of y and observe after "viewing 21 of X is displayed" forward arrow not available
same happening in case of team navigation
also count of total users and teams is not correct

3. Update link on user/team profile page from "Company Directory" to "Company directory"

4. Centre align team lead/manager name on user/team profile page with image

Issues on company dashboard OKR gadgets 🐞

Issues on company dashboard OKR gadgets

Issue 1
Confidence status and objective count in company OKR gadget is not in sync (Refer attached screenshot 1)

Issue 2
Y-axis in team OKR gadget on company dashboard displays duplicate numbers (Refer attached screenshot 2)

Confidence status and associated count on my dashboard not proper for ready/in progress objectives 🐞

Confidence status and associated count on my dashboard for objective not proper for ready/in progress objectives

Refer attached screenshot

Inappropriate error message is displayed while creating request feedback and feedback by is kept empty 🐞

Inappropriate error message is displayed while creating request feedback and feedback by is kept empty

Steps:
1. Open request feedback popup
2. Add appropriate details and keep feedback by receiver field empty
3. Click on save
4. Observe error msg displayed is for inactive/deleted users

Expected : Appropriate error msg should be displayed when feedback by is kept empty while creating request feedback

...

  • Support for sprint variables 🎁


    Background

    Many teams don’t use versions in Jira, instead, they use sprints in Jira. Some also use sprints along with versions in Jira to manage their projects. In ARN we mainly support versions and version variables to generate release notes. Hence, we need to provide support for sprint variables like version variables in ARN.

    User Story

    As a user I want to insert sprint variables in my ARN templates so that I can publish release notes for the sprints created in my Jira project(s).

    Description

    Addition of Sprint Variables in Variables

    • In all types of templates, we can add various types of variables. We will include following sprint variables in that list :
    Sprint VariableDetails
    name: The sprint name (String).
    goal: The sprint goal (String).
    startDate: When the sprint started (Date).
    endDate: When the sprint is planned to end (Date).
    completeDate: The actual date of ending the sprint (Date).
    state: The state of the sprint (String: 'future', 'active', 'closed')
    • As the no. of variables in the select menu have increased, we will convert this select menu into ‘Grouped Select Menu’

    ( Refer: https://atlassian.design/components/select/examples#grouped-options ) like this

    Image Added

    • Variables shall be grouped like this:
    Project
    projectName
    projectld
    projectKey
    Version
    version Name
    versionDesc
    release Date
    versionld
    versionURL
    startDate
    Sprint
    sprintName
    sprintGoal
    sprintStartdate
    sprintEnddate
    sprintCompletedate
    sprintState
    Date & Time
    timestamp
    currentDate
    currentDatetime
    Users
    userName
    userEmail
    Confluence
    confluence URL
    • System shall replace the sprint variables with the actual value for a sprint which user shall select on the sprint selector screen. (similar to the way value of version variables is replaced in template preview currently)

    Sprint variables in the JQL

    Just like version variables, users can use multiple sprint variables in the JQL.

    project = "11915" and Sprint = ""
    project = "11915" and Sprint in ("","")
    • Sprint variables used in the JQL like this shall be accepted in the JQL validation.
    • Users can also use sprintName variable instead of the sprintId variable and system shall recognize the sprint just like versionName variable is honored instead of versionId variable in the JQL.
    project ="11915" and sprint in ("","") 

    Version Selector screen - in-project

    • Currently when version variables are used in the template or the JQL , then on version selector screen, system asks the user to select corresponding versions for each of the version variables used in the template.
    • Same way when users have included sprint variables in the template or the JQL, then on version selector screen, system shall also ask the user to select corresponding sprint along with the version.

    Refer:

    Image Added

    • No of sprint selectors shown on version selector screen shall depend upon no of unique sprint variables used in the template.
    • Similar to versions, selecting sprint on version selector screen shall be optional.
    • System shall show all the sprints available in the project in sprint selector irrespective of their state.( 'future', 'active', 'closed' )
    • If the template has no version variables but only sprint variables, then on version selector screen only sprint select menus shall be shown.
    • Change in message shown on version selector screen
      • In case of multiple versions, we show the message on version selector screen. This message shall be changed to a generalized version like this.
        • When multiple version and sprint variables are used

    Multiple variables used

    This template uses multiple variables, please select values for each one.

    • When no version or sprint variable is used.

    No variables used

    This template does not use any variables, thus no inputs needed from you.

    Version Selector screen - cross-project

    • In case of cross project version selector screen, user has to select the project before selecting the version variable.
    • Similar to this, system shall ask user to select the sprint below the corresponding project selector.
    • few examples
      • when there are two version variables and two sprint variables included in the template

    Image Added

      • when there is one version variable and two sprint variables included in the template

    Image Added

      • when there is no version variable and two sprint variables included in the template

    Image Added

    • Change in message shown on version selector screen
      • In case of cross project, we show the message on version selector screen. This message shall be changed to a generalized version like this.

    Template with cross project multiple variables

    Template involves use of multiple variables. Please select a project & corresponding values for each variable.

    Rule Triggers

    • On the rules create/edit page, we will include one more trigger i.e. Sprint completed
      Refer:

    Image Added

    • When this trigger is selected, rule shall gets triggered whenever a sprint is marked as completed in the project.
    • This rule trigger shall be available only in in-project ARN screen presently.

    Acceptance Criteria

    • Users should be able to include sprint variables in the template in all types of the templates.
    • System shall ask users to select sprint on version selector screen when sprint variables are used in the template. (in both in-project and cross-project screens.)
    • User should be able to use ‘sprint completed’ rule trigger and system shall trigger such rule whenever any sprint is marked as completed in the project.
    • All other features of ARN shall work as it is.

  • Support for Confluence's 'Expand' macro 🎁


    Background

    Currently ARN cloud app supports following macros for Confluence (in the templates)

    • Info
    • Tip
    • Note
    • Warning
    • Table of contents
    • Children display
    • Panel
    • Page Properties
    • Jira Issues / Filter

    Currently there is no support for ‘Expand’ macro in ARN confluence template. One common request is to allow ‘Expand’ macro within these templates.

    User Story

    As a user I should be able to include ‘Expand’ macro in ARN confluence template so that I can publish it in my confluence release notes.

    Description

    1. We’ll be adding support for new macro called ‘Expand' in add macro drop down in add/edit confluence template screen.
      Insert Macro:

    Unable to render embedded object: File (f342f9b3-1a0d-4c42-9531-9dfe8328170e#media-blob-url=true&id=78cc17b7-3581-4741-b455-f5e495f88ec7&collection=contentId-3418914831&contextId=3418914831&mimeType=image%2Fpng&name=image-20211004-131910.png&size=239223&width=1049&height=567&alt=) not found.

    1. When user selects ‘Expand’ macro, it will open a pop up to capture additional details related to macro.

    The pop-up will have two fields

    Title :
    Tinymce text editor (which is used for all other macros) with following changes

      1. Title defines the text that appears next to the expand/collapse icon.
      2. Default title will be shown in the text box as “Click here to expand... “
      3. If required, user can modify the title text as per his need.
      4. Confluence does not allow enhancements in the text such as format, bold, italic, font-color, font-size, background color, Text alignment .
      5. Include options to insert variables and stats
      6. Below the text editor, show this text as tip - “This text will be shown in single line as title of expand macro in the generated page.”

    #Content :
    Tinymce text editor (which is used for all other macros) with following changes

        1. Add support to insert
          1. Link
          2. Files & Images
          3. Table
        2. Disable support for options in text editor as they are not supported in confluence for expand macro currently.
          1. Text alignment options such as right,, center, justify align
            1. All the text will be left aligned by default
          2. Indentation options i.e. decrease indent & increase indent

    Refer this wireframe:

    Image Added

    1. When added, this macro would appear same as other macros within the ARN template

    Unable to render embedded object: File (fbaccf7b-f62d-40d0-bda3-4ada273e568a#media-blob-url=true&id=120f8547-b194-4a3c-aec4-ccd5ab685691&collection=contentId-3418914831&contextId=3418914831&mimeType=image%2Fpng&name=image-20211004-132915.png&size=155058&width=953&height=381&alt=) not found.

    1. When user previews the template, it will show the details of macro like other macros in following format
    Macro NameParameters
    Expandtitle : Expand Title
    rich-text-body:
    Expand details

     

    5. When confluence page is published using this template, ARN will insert macro with the captured details.

    Refer for markup details : https://support.atlassian.com/confluence-cloud/docs/insert-the-expand-macro/

    Expand macro should support confluence new editor

    Acceptance Criteria 

    • User should be able to select and insert expand macro in confluence template.
    • ARN should insert expand macro in the confluence page created/updated through rule execution.
    • Expand macro inserted by ARN on confluence page should get rendered as expected.
    • All other functions of ARN should work as it is.

  • Supporting custom time zone configuration  🎁


    User story

    As a user I shall able to select my own time zone which can be used for showing date/ time variables while publishing release notes so that I can show time as per my preferred time zone

    Description

    • This will add a time zone configuration so that user can use it to show time as per his choice of time zone
    • Below are changes required

    Changes in Jira admin facing configuration screen → Date format

    • We’ll add a new configurations in the Configuration → Date format screen viz.
      • Default time zone
    • Revised fields shall be as below
    FieldControlDescription
    Default time zone [ NEED TO ADD ]Combo box
    • Mandatory
    • System shall give error message as ‘This field is mandatory’ when no value is available
    • Default value shall be (GMT +00:00) UTC
    • Drop-down should show list of standard time zones
    Date format [ AVAILABLE ]Text box
    • Mandatory
    • System shall give error message as ‘This field is mandatory’ when no value is available
    • Default value shall be ‘dd/MMM/yyyy
    • System shall validate the format entered by user and show the relative eg. as help text
      • This help text shall be refreshed according to the format entered by user
    Complete date format [ AVAILABLE ]Text box
    • Mandatory
    • System shall give error message as ‘This field is mandatory’ when no value is available
    • Default value shall be ‘dd/MMM/yy h:mm a
    • System shall validate the format entered by user and show the relative eg. as help text
      • This help text shall be refreshed according to the format entered by user

    Actions

    • There shall be actions viz
      • Reset
        • This will reset the configuration to default configuration
      • Save
        • This will validate and save the configuration as changed by user
    • Refer
      Image Added

    Affected variables / Fields

    • PDF Variables - [date]
    • Variables - Thu May 19 09:49:25 UTC 2022
    • Variables - 19-May-2022
    • Variables - 19-May-2022 9:49 AM

    Migration & New Installation

    • For migration of existing instances & new installations, values shall be set as below
    FieldMigrationNew Installation
    Default time zone [ NEED TO ADD ]
    • Set default value : (GMT +00:00) UTC
    • Set default value : (GMT +00:00) UTC
    Date format [ AVAILABLE ]
    • Keep existing value
    • Set default value : ‘dd/MMM/yyyy
    Complete date format [ AVAILABLE ]
    • Keep existing value
    • Set default value : ‘dd/MMM/yy h:mm a

    This change is applicable only for ARN Cloud App (Free and Paid). For Server app, date settings are directly referred from default Jira settings.

    Acceptance criteria

    • User shall able to configure Time zone, Date and complete date format
    • Configured format shall be used while displaying date or time in ARN
    • All other features of ARN shall work as expected

 

Improvements (0)

No improvements were part of this release.

 

Bugs (11)

  • [Pre-production] - In template preview JQL and Stats as it is displayed  🐞


    Steps to reproduce -

    1. Go to template tab
    2. Edit / create any template
    3. Add JQL sections and stats in template
    4. Save and preview the template

    Expected Result - In template preview JQL and stats should be replaced with respective values.

    Actual result - In template preview JQL and stats sections as it is displayed.


  • [PDF template] - In ARN cross project after preview pdf not generated 🐞


    Pre-Condition -

    1. User should be logged in to jira

    Steps to Reproduce -

    1. Open ARN cross project
    2. Go to template tab
    3. Create pdf template
    4. Save the template
    5. Preview the template

    Expecte Result - The PDF should be generated and we should be able view the pdf.

    Actual Result - process only running on preview button but pdf not generated.


    Note- In rule action preview if we trying to download attached PDF then following error displayed

    {{

    {"status":500,"error":"Internal Server Error","message":"","timeStamp":"Thu Apr 07 11:14:55 UTC 2022","trace":null}

    }}


  • For unauthorized project in "ARN in-project" screen "ARN cross project templates" are displayed 🐞


    Pre - Condition -

    1. Two users are there in single project
    2. Users should be logged into jira
    3. ARN should be opened

    Steps to Reproduce -

    1. Give project permission to one user.
    2. And remove same project permission for another user.
    3. Then for unauthorized user open ARN in same project.
    4. Go to templates tab.

    Expected Result - In templates tab for unauthorized user in template tab ARN in-project templates should be displayed.

    Actual Result - In ARN in project templates tab cross project templates should be displayed.


  • [Confluence Integration] - Unable to add / update Confluence integration with valid details 🐞


    Pre-Condition - 1) User should be logged in to jira

    2) ARN should be opened

    Steps to Reproduce -

    1. Go to cog wheel & open Apps menu
    2. Open ARN configuration tab
    3. Go to integrations tab
    4. Try to add / Edit Confluence integration

    Expected Result -

    1. If we try to edit existing confluence integration Then Existing values should get updated for respective integration only
    2. If we try to add new confluence integration then new confluence should be saved.

    Actual Result -

    1. Try to edit existing confluence integration - If settings saved successfully then already added integrations are automatically updated
    2. Try to add new confluence integration - If we enter all valid details still “Invalid login credentials“ error is displayed

    NOTE - For JSD also same issue is there.


  • Scheduler blocking DB connections 🐞


    Scheduler we use on cloud version, at times, blocks DB connections, and that slows down the overall performance of app.


  • Rule actions triggered multiple times for version release trigger 🐞


    Rule actions with version release trigger getting executed multiple times in some cases.

    Two customers have reported this recently for Paid cloud app


  • Lanuguage translations missing for rule exection status in logs tab 🐞


    Pre-condition - 1) User should be logged in

    2) release notes cross project.

    Steps to Reproduce-

    1. Change the language
    2. Go to ARN rules tab.
    3. Create a rule
    4. Add Email, Confluence ,Post actions, JSD
    5. Click on RUN button
    6. Trigger the rule by selecting any version
    7. Go to logs tab

    Expected result- Rule should get triggered successfully language translation should applied to the “Rule action execution is in progress“ & “Rule action added to the queue.“ messages.

    Actual result - language translation not get applied to the “Rule action execution is in progress“ & “Rule action added to the queue.“ messages.

    Note -

    1. This is applicable for all servers

  • [logs listing] - Version not displayed after rule tiggered successfully 🐞


    Pre-condition - 1) User should be logged in

    2) Open automated release notes

    Steps to Reproduce-

    1. Go to rules tab
    2. Create a rule
    3. Add Email, Confluence ,Post actions, JSD
    4. Click on RUN button
    5. Trigger the rule by selecting any version
    6. Go to logs tab

    Expected result- Rule should get triggered successfully and entry should be displayed in logs and in logs listing selected version should be displayed.

    Actual result - Rule triggered successfully and entry also added to logs but in logs listing selected version not displayed.

    Note - This is applicable for all servers.


  • Error when stats JQL returns more issue count 🐞


    Steps to reproduce:

    • Go to ARN and create/edit PDF template
    • Include a stats section with a JQL which will return more than 600-700 count.
      or
    • Include multiple stats sections whose cumulative count exceeds above no.
    • Preview template
    • Open generated PDF
      • Actual : File does not open, it gives this error

    Image Added

      • Expected: PDF should open and show expected data
    • Use same template for some other template type (e.g. email)
    • Preview template
      • Actual : Sometimes preview gives this error

    Image Added

    Same error appears in rule action preview

      • Expected: template preview should work and reproduce the data as expected

  • Release page contains multiple html, body & head tags 🐞


    1. View source on a release page, e.g. view-source: https://teamten7.release.page/ten7-com
    2. Check contents of any `card-body` div
    3. See multiple html, head, body tags that are present – there should only be one html, head, body per document, see screenshot.

  • Showing rule execution entry in logs immediately 🐞


    Steps to reproduce:

    1. Go to ARN and run any rule
    2. Go to logs screen immediately after the rule is run

    Expected: Entry for the rule just executed should show in logs screen

    Actual : It takes around 1 minute (sometimes more than that) to show the entry. User needs to click on refresh repeatedly. Sometimes, some users assume rule is not triggered, and they go back to rules and trigger rule again. This leads to multiple executions of same rule.

    Corrective Action : Logs section should show the entry immediately after the rule is run. If rule execution is not completed, it will show the status 'in progress' in logs. The status shall get updated as and when the rule execution is completed by the system.


 

...

Raise a ticket on our service desk, if you need any help.