-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Issue Summary
The filter 'Where I am a participant' fails to fetch the issue when the user is a Reporter and a Participant.
Steps to Reproduce
- Install JSM
- Create a JSM project
- Create an issue (Now, you are the Reporter)
- Add yourself as the 'Request participant'
- Go to Customer portal and filter for the issues by selecting the option 'Where I am a participant'
Expected Results
The issue that we created gets displayed.
Actual Results
The issue is not displayed unless we remove the user from the 'Reporter' field.
The call that is triggered is 'https://jira/servicedesk/customer/user/requests?reporter=others&status=open&page=1' which is why it filters any issues where the current user is not the reporter.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Versions Tested
Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below:
Testing Requirements | Version | Affected Version |
---|---|---|
Customers Reported Version | 10.3.2 | Yes |
Most Recent Bug-Fix Release | 10.5.1 | Yes |
Previous Major Release | 10.0.0 | Yes |
Most Recent LTS | ||
Previous Supported LTS | 4.20.13 | Yes |
Other Versions.. | 4.17.1 | Yes |
(Add rows as needed) |
- links to
[JSDSERVER-16156] The filter 'Where I am a participant' fails to fetch the issue when the user is a Reporter and a Participant.
Support reference count | New: 1 |
Affects Version/s | Original: 10.3.2 [ 110306 ] | |
Affects Version/s | Original: 4.17.1 [ 95194 ] | |
Workflow | Original: JAC Bug Workflow v3 [ 4517449 ] | New: JAC Suggestion Workflow 3 [ 4517310 ] |
Issue Type | Original: Bug [ 1 ] | New: Suggestion [ 10000 ] |
Priority | Original: Low [ 4 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Interest [ 11772 ] |
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 1007856 ] |
Description |
Original:
h3. Issue Summary
The filter 'Where I am a participant' fails to fetch the issue when the user is a Reporter and a Participant. h3. Steps to Reproduce * Install JSM * Create a JSM project * Create an issue (Now, you are the Reporter) * Add yourself as the 'Request participant' * Go to Customer portal and filter for the issues by selecting the option 'Where I am a participant' h3. Expected Results The issue that we created gets displayed. h3. Actual Results The issue is not displayed unless we remove the user from the 'Reporter' field. The call that is triggered is 'https://jira/servicedesk/customer/user/requests?reporter=others&status=open&page=1' which is why it filters any issues where the current user is not the reporter. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available h3. Versions Tested Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: ||Testing Requirements||Version||Affected Version|| |Customers Reported Version|10.3.2|_Yes_| |Most Recent Bug-Fix Release| | | |Previous Major Release|10.0.0|Yes| |Most Recent LTS| | | |Previous Supported LTS|4.20.13|Yes| |_Other Versions.._|4.17.1|Yes| |_(Add rows as needed)_| | | |
New:
h3. Issue Summary
The filter 'Where I am a participant' fails to fetch the issue when the user is a Reporter and a Participant. h3. Steps to Reproduce * Install JSM * Create a JSM project * Create an issue (Now, you are the Reporter) * Add yourself as the 'Request participant' * Go to Customer portal and filter for the issues by selecting the option 'Where I am a participant' h3. Expected Results The issue that we created gets displayed. h3. Actual Results The issue is not displayed unless we remove the user from the 'Reporter' field. The call that is triggered is 'https://jira/servicedesk/customer/user/requests?reporter=others&status=open&page=1' which is why it filters any issues where the current user is not the reporter. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available h3. Versions Tested Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: ||Testing Requirements||Version||Affected Version|| |Customers Reported Version|10.3.2|_Yes_| |Most Recent Bug-Fix Release|10.5.1|Yes| |Previous Major Release|10.0.0|Yes| |Most Recent LTS| | | |Previous Supported LTS|4.20.13|Yes| |_Other Versions.._|4.17.1|Yes| |_(Add rows as needed)_| | | |