|Cannot create events||Fix create events||Fixed|
|Task - Rework details||Task module - Rework details node is not working. Error thrown and edit box for entering text is not displayed||Fixed|
|Owning Group on Ad Hoc Task cannot be changed||*Description*: When Ad Hoc Task is created and initial Owning Group is dedicated, after Save any change of the Owning Group is reverted to the one initially saved.
*Steps to Reproduce*:
# Click on the New button on top left corner next to the log
# Select Task
# Fill Assign To field and rest of the required data
# Click on Save Task button
# Once saved from the list select the task
# Click on Owning Group value and search for new group
# Save changes
# Reload the page
*Actual Result*: After Save action when Owning Group value is edited the value is reverted to the old one.
*Expected Result*: Change should be saved and stay as provided after save action.
|AFDP-3202 i18n for Complaint component link tooltip||Complaint has icons at bottom linking to components. The tool tip text is display as English only. Implement i18n to display them for different languages.||Fixed|
|Add Plain Form button||1. Log into the application.
2 Click on Admin on the sidebar.
3 Under the Forms folder, click on Form Configuration.
4. Click the Add Plain form link button
Without selected target, the Add Plain from button is displayed as disabled but, if you click it , still redirects to frevvo form page.
|New Person - Details rich text field||On "New Person" form, there should be a text field for entering person's details. Data entered here will be shown in "details" node under People module||Fixed|
|Simple Search - Type Ahead Issue||Type Ahead needs to word wrap.||Fixed|
|Organization > People table should display the Person Type or Relationship Type||People table should display the Person Type or Relationship Type||Fixed|
|User management: allow user to reset their password from the login page||Today the user can reset their LDAP password after they have logged into ArkCase. But if their password has already expired, they can't login.
Update the login page to allow resetting the password from there... Ideally only allow this if they already failed to login due to password expiration... but if that is pretty hard, then always show it. Obviously the user somehow has to provide their correct current password... if there is no way to validate they have entered the current current password (since it has expired already) then we won't implement this feature. I hope if the current password is wrong, you get the wrong credentials exception, which I hope is different from password-expired exception.
|When at least one tag is not highlighted, "Add tag" button should be disabled||1: Login as user that have permissions to Cases/Complaints
2: Open one already inserted case/complaint
3: Click on Tags sublink under case/complaint
4: Click on "+" sign
5: Insert new random tag and click "Add button".
Expected result: Notification message is displayed informing that user didn't successfully entered tag. "Add tag" button is disabled until at least one entered tag is highlighted.
Actual result: The pop up is closed, tag was not successfully inserted. No notification that tag is not successfully entered.
|AFDP-3519 Create Wireframes for Email Configuration in Admin||Create Wireframes for Email Configuration in Admin
3 new sections
1. Email Templates Table
2. Email Merge Fields Table
3. Email/Action Link Table
|AFDP-3519 Update the front-end for sending emails.||The front-end services that are used to send emails, should be updated in order to use the new templates that are associated with actions by object type.||Fixed|
|AFDP-3519 Front end for interacting woth the REST API for updating the email templates.||Front-end should be created to interact with the REST API for managing the email templates.||Fixed|
|AFDP-3519 Update email sending service.||The beck-end services that are used to send emails, should be updated in order to use the new templates that are associated with actions by object type.||Fixed|
|AFDP-3519 Create services that the REST API will use in order to store, read and update the templates from the file system||Create a service for creating, updating, retrieving and deleting of the email templates used by the REST controller.||Fixed|
|Close Complaint assigns the task to wrong user||Close Complaint assigns the task to Ann Administrator regards of who you chose to approve.||Fixed|
|Search results, selected a Person. Navigated tree issue||Search results, selected a Person.
Navigated to the Person in the content pane (right side), but the Person was not selected in the browser tree.
|The newly created Organization within a Case missing link||The newly created Organization within a Case link is missing the Organization ID. Not sure if that's because the Organization is not being created or another reason. I couldn't find the newly created Organization, so I assume that was the problem.
|Uploaded a Document within a Complaint of type Other issue||Uploaded a Document within a Complaint of type Other and the Creator was set to ACTIVITI_SYSTEM versus "Jim Smith"||Fixed|
|New Organization > Details rich text field is missing||New Organization > Details rich text field is missing
When creating a New Organization, there is no place to add "Details"
|Added an Organization to a Complaint/Case Issue||Added an Organization to a Complaint/Case and then navigated to the Organization to see if the Complaint/Case was linked and it did not show.
Navigate to Complaints
Select Complaint > Organization node
Add an existing Organization (ACME, Inc)
Organization shows in table, but when I click on the linked Organization it navigates to the Organization without the Complaint being linked
Organization > Complaints
I noticed the same for Cases also
|People Filter Navigate Issue||People Filter
Navigate to People module
Enter filter term
No change in the browser tree. Expected to only see the items that matched the filter
|Organization module - Related Organization node functionality issues||For the Related Organization node in Organizations Module, there are few issues/defects that has to be fixed:
Add/Edit/Delete functionality has problems:
- you cannot add existing organization
- for adding new organization, "new organization" popup form is opened, but error is thrown when adding data for ID. People node is not working (empty)
Creating Related Organization does not result in a new Organization or a link between an existing Organization.
|People module - Related People node functionality issues||For the Related people node in People Module, there are few issues/defects that has to be fixed:
- Add new person should show Relationship type
- no way to edit the related person table
- The new related person should show in the people tree
- Edit/Delete related person doesn’t work
- form buttons should be consolidated as other forms
|People module - Organizations node functionality issues||For the Organizations node in People Module, there are few issues/defects that has to be fixed:
- Edit/Delite Organization issue
- form should be consolidated as other forms ("+" in the black header for adding new picture, "edit" and "Delete" buttons on the right of each line)
- There is no way to see what organization is the primary from the table
- Doesn’t hyperlink to the Organization in the Organization Module Correctly
|Reorganizing New People and New Organization forms to be in-line with Wireframes||"New People" and "New Organization" forms/pop-up windows opened when user is trying to add new person or new organization from some object (Case, Complaint, People or Organization) should be improved:
- Mandatory fields to be noted (Asterisks and Red-boxes for mandatory fields)
- "Cancel" button to be added (for New Organization window)
- Picture should not be mandatory for adding new Person
- "ID" - No need for Identification ID field (Identification number is enough)
|Admin - Email Template Configuration||Admin - Email Template Configuration
- Need to have the ability to add and update default body text for email templates
- Need to have the ability to link the email templates to actions in the system to dictate when the emails are fired manually/automatically
|When complaint is created additional event is added in history - Complaint Updated - Document Uploaded||1: Login as user that have permissions to complaints
2: Click on New/Complaint
3: Insert all required data and save.
4: Click on history link ,
Expected result: only one event is created "Complaint Created",
Actual result: except Complaint Created is created additional event: " Complaint Updated - Document Uploaded" even though user have not uploaded
|Search module - Assignee = Mail Services||1.Log into the application.
2. Click on search in the sidebar.
3. Enter your search query in the box and click search.
Notice that Mail-services is the Assignee in the search results, but that value needs to show in the facets.
|FOIA - "Start Working" button redirects to empty request||1: Login as user that have permissions to navigate to queues
2: Click on "Start Working" button,
Expected Result: should redirect to first item from the queue and open it,
Actual Result: redirects to this link: https://star.arkcase.dev.armedia.com/arkcase/home.html#!/request-info//
id is missing in the link. I spoke to Dragan, this functionality exist and is working in Bactes project
|Upgrade Solr to newest version - v5.4||Upgrade Solr to newest version - v5.4||Fixed|
|Upgrade Pentaho to newest version - v6.1||Upgrade Pentaho to newest version - v6.1||Fixed|