- Last Active
@JeehongMin This only works for assignees also identified via the XML report upon publishing, excluding members of projects who were not identified in the publishing process. However, I will close this discussion as a "by design" situation. Thank…
@JeehongMin I greatly appreciate the clarification. With that said, specifying an assignee to a violation has been working with adding members to the project as you and @Jromero described. However, it only works if I search by login name (byronp@dom…
@Jromero Thank you so much for the confirmation! I've tested this and you are correct to say that the user must be a member/leader of the project. However, I noticed that I can only assign the violation and view the user via their login name, e.g…
@Mark Lambert Thank you for the response, Mark! This is good information to know in case we want to isolate permissions by user or group. However, we are currently looking into applying permissions at a project-level, not user or group level. The…
@Jromero Thanks for the confirmation. In that case, unless that option is offered in a future release, we will then have to consider an alternative approach or a different workflow.
@Jromero Thank you for the confirmation. If I understood your question correctly, the Language/Functional Tool we are using is C/C++test DTP Engine 10.3.2 (the command-line one). Regarding the workflow, there are primarily 2 places that a report …
Thank you for the quick response, @Jromero! I definitely understand the concern with that. I should also mention that we already have LDAP connected to our DTP server, so any user with a domain account can already login to our server and we are not …