I have set up an alias "approve" set to transition a service request to the next workflow step. Using a test case, that seems to work fine but it sees that the validation is failing. I have assigned the issue to myself and set myself as the approver, and I have admin, developer, and team member access to the project. According to the results, the test case is running as me, as expected. Below is what I am getting in the workflow section after running the test case (abridged):
The issue has not been modified, nor is 'Approved' not valid, when I look at the issue after running this, I can approve it manually in the UI without any problems. I have also run the permission checker and I have no issues editing the issue or transitioning the issue.
So JEMH cannot approve or deny issues through email any longer using the standard approval logic in Service Desk:
This is deceptive as all of the documentation says it is possible.
I do not think that the documentation is deceptive or misleading, all of the documentation is written in relation to standard JIRA workflows, likely the documentation was written before JSD approval's were implemented, JSD approvals are an additional feature on top of workflow transitions and have never been supported by JEMH.
We are investigating adding support for the JSD approval process, the issue you link above tracks the progress of this, please comment and vote on the issue so that we know it needs prioritising. Currently JSD is blocking the validation of the workflow transition, this will require investigation to see if we can resolve this.
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG