ContributionsMost RecentMost LikesSolutionsAction Items not loading in Web GUI Home Page, Desktop GUI Collaborator version: 12.1.12101 Java: 11 Some of developers could not see any action items (reviews) on the Web Client home page and desktop GUI. But they can access directly from url and do some operations except upload file. SolvedIF THERE IS NO DEFECT ON A FILE, DON'T UPDATE THE FILE If a participant doesn't add defect on a file when there are deleting, adding or changing lines on file, the file will not be updated and will be seen with the file name. Scenario: 1- Add fileX 2- No add a defect on fileX 3- Update fileX 4- WARNING: The file does not have DEFECT, so the file is not updated. It is necessary for control of changed files with defects and prevent uncontrolled change. Could we do that with Trigger on the Added Files field? Show history of all items on checklist Hello, Can you add a button for all items on checklist that will show item history who checked or what participant did? In addition, if there is different answers on a checklist item, history button can be colored like "red". Thanks. Re: Permission to Create Defect - Role Template Author can write his / her own opinion in the comment field. Also, when the Reject Button is added next to Mark Fixed, the author will be able to reject the defect. As different perspective, the author found the defect that reviewer did not see. In this case, there is a chat section where the author can communicate with the reviewer. Author can send defect request. Not opening the defect.Maybe that's the solution. Re: Permission to Create Defect - Role Template Hiyimy, That's exactly what I'm talking about. 1. None => Don't create or modify 2. Create => Create defects 3. Create and Edit 4. Fix or Reject ....... Thanks. Hi MrDubya, When creating defect asan reviewer, an moderator, or another role, the Author may only reject or fix the defect. Reviewer -> Defect Finder Author -> Defect Solver I think there should be this restrictions for the author in role template. We would like to restrict this to the Author rather than to have him create a defect individually. Suppose we said to authors that should not create an defect and created it. When you deletethe defect again, it will appear in the log. Is such a restriction unnecessary? Could you explain if it's unnecessary? Thanks. See who reviewed the file For example: When you accept in chat field, in the Review General Page - the field of files, the user is seen with Approved icon. Could you add the feature that when the user open file, add "Eye icon or something" to be seen with "Eye icon or something" in the Review General Page - the field of files. GUI Select File according to extensionsIn collaborator GUI Client, could you add choose files in a folder or subfolders according to file extensions. For example, choose *.py files in a folder and its subfolders to review. 1- It can be filter that shows all the files recursively based on file extension. Filter should be modifiable. 2- It can be regular expression field to search files or folders recursively and then select.Jira Reporter Username - Export IssueHello, When I export issue to Jira, I have some problem about Jira Reporter. Scenario: Note 1- Jira and Collaborator have same LDAP Authorization. 1- Export Issue after editting Defect with userA. 2- When I visit to Jira Issue, REPORTER = Jira LDAP admin account. I would like to see the reporter as userA in Jira Issue. Is it responsibility of Jira or Collaborator or both? Regards.Re: Review Template Disable&Edit Scenario: 1- Go to Review Template 2- Disable 3- Enable 4- Edit 5- Automatically a new template that is the same with editted Review Template is created by Collaborator. I need Disable->Edit->Enable like Checklist Template. Re: Permission to Create Defect - Role Template When set Can Change Own Defects to None and Can Change others' defects to fix/edit: 1- Edit - Author can change defect custom fieldsanddefect comment of others. 2- Author can open defect but could not change own defect. I tried to mention about that: 1- Author can not changedefect custom fieldsand defect comment of others. 2- Author can not create defect. 3- Author can track externally or export issue. 4- Author can fix or reject defect.