eTask Limitations and Work as Design notes

Release Notes

1. Can’t view file directly on MS Teams when click “Open in Teams”.
   a. Click on Action menu of attached item
   b. Click on “Open in Teams”.
   c. There is an “Unknown error” in Teams.

2. Text highlighted in dark/white background when copy and paste in section when changing MS Teams Theme mode.
   a. Copy text in a section when on Light Theme.
   b. Change Theme mode and Paste it on section.
   c. The color of text will be kept as on Light theme. Doing vice versa by switching Theme mode will occur this limitation.

eTask Form

1. eTask Mobile App: Create/Update task by eMA, the history will not be logged as Created/Updated by Mobile.
   a. Currently, we treat a task as a work needs to be done, does’t matter where it is created or updated.
   Note: This also apply in “Import” and “Excel Sync” feature.

eTask Settings

1. When the sync job is running, and then turn off this project. On grid still show items of this project. If you want to completely turn off the synchronization of the project, you should remove Sync job belong to that project too.
2. Sometimes sync job is disappeared. Try to reload the eTask tab.
3. The “Test query” function is failed when synchronize more than 400 tasks from Planner source. It depends on the Planner connection, try to narrow down your query to test.
4. From Jira source, creating a task related to a Story. After synchronizing to eTask, that task will not show Story in Task detail. But user can choose Story for the task later.
   This happened because eTask treating Story as category when Story is treated as work item in Jira.
5. Rename Planner source and the Source name isn’t changed on the filter pane/ sync job/item detail.
6. When rename project from vsts source, can’t save tasks/bugs before clicking Sync Now. Changing project name might cause the synchronization failed because it won’t get the correct project name. Be concern when changing project name in VSTS.
7. The progress bar shows the progression of the sync job by percentage incorrectly. This occur sometime depending on inter connection. You may leave it synchronize and come back another time.
8. In VSTS, rename phase will cause error to tasks/bugs in eTask because we can’t know which phase is changed. Please be considered when changing phase name has existing tasks in it.
9. Rename project name in Jira. The project name will not be changed in eTask. If you want to change project name, please remove, and add the project again.
10. With Planner source, the status of import will display “ Too many request” in log file when import more 200 items.
11. Sometime the system show “import failed” but data is still imported fully. This occurs when you try to import more than 150 items. The system may return failed, but the background process is still working. You can try to re-check your data by Export.
12. Can’t import task/bug in Teams app (Display “Missing configuration for import.”). Currently, the best way of import is via MS Teams on Web browser.
13. Changing choice type may occur errors with your existing tasks/bugs as the selected option may be deleted.

Others

1. Using Edge browser and click on PM Dashboard tab, the PM Dashboard is loading forever. Recommended to use Chrome.
2. Switching between My Task, My Bug, My Progress too many times, the PM Dashboard is loading forever. Please refresh the page, if the problem is still occurred, try to ctrl + F5 for reload with clear cached.
3. Create a new channel but it does not have default Events. This may occur sometime as too many requests on server. You can try again in a short time.
4. On Outlook App, the image does not show in body when the inserted image larger than 300kb.
5. Keeping format of text when pasted content from web browser page.
6. The maximum image size in body that eTask allows is 4 MB.
7. The tasks of Planner source could not be updated by eBot.
8. Try to delete task/ bucket/ project planner, the tasks are removed in Planner source but in eTask source, tasks aren’t removed (Loading after save tasks). You can remove completed by delete the source in Settings or delete channel.
9. For tasks/bugs using Planner/Jira source, deleting from their original source but they won’t be deleted in eTask. But if you delete those tasks in eTask, the tasks will be deleted in Source.
10. When body & comment have image, the content will display thumbnail of image in email. Because the email will be broken UI and does not allow too large email 10MB.
11. Break UI “This is an automated email…” at end of the email. This happened for some email system such as Outlook or Mail in Windows.
12. On Jira, if the task/bug belongs to status is “Done” and the sprint is “Completed”, these tasks will not be saved as it is already done in Jira, it cannot be edited.
13. Tasks aren’t sync when using new host name of the Azure DevOps “dev.azure.com/mycompany/”.
14. For tasks with source VSTS, they cannot be changed status when status from VSTS is “Remove” even though you mapped status.
15. Mapping status displays “Invalid” after removing that status from VSTS, Jira source.
16. Deleting project from VSTS/Jira source and in eTask, the project, sync job, item is still shown but when opening the items, it can’t get phase/bucket. Please be concern when deleting a project which associating with eTask.
17. When you change the source after entering the body of a task, the format of the body will be reset because each Source can support different HTML format. Try to allocate your source first and then insert body for better viewing.
18. Using group by Assign To, the grid will display each assignee in each page.
19. Assign to field doesn’t display all assignee when the name of assignee is too long. But you can hover on the avatar to display the user detail, and hover on the number to show all the assignees.

Comment

Was this article helpful?

Write your comment

Thanks For Your Feedback