![]() ![]() When Bob saves his changes the version is incremented to 2. This version is then checked when saving (often by providing the version in the sql query's where clause) and rejecting the update if an old version is being updated.īob and Sally are editing version 1 of the story. This last write win is undesired.īetter would be to use an optimistic locking mechanism where a version/revision number is saved on the story that is incremented each time it is modified. Bob saves his changes first and so when Sally saves her changes she has overwritten Bob's changes without even knowing it (without performing some forensics in the story's history). Using JIRA Server? See the corresponding suggestion.īob and Sally are both editing story 123. There is a particular one for approvers there.NOTE: This suggestion is for JIRA Cloud. Make sure that the relevant notifications are enabled, and set to send to the right users. That is where you set up notifications for your customers including your approvers. These are configured per project, In the section marked "Customer Notifications" For Jira Service Desk, there are Customer Notifications. That of course doesnt work for JSD Customers, who are unlicensed. If you do not have a licnese, then nothing you do in there will be relevant. They key thing to realize with that one is that you have to have permission to log into jira and see the issue in order to get those notifications. ![]() That is controlled by Notification Schemes, permission schemes etc. The first thing to realize is that when dealing with JIRA Service Desk, there are two completely separate notification systems I am very new to the administrator functions of Jira, so painfully explicit step-by-step instructions would be very much appreciated. I desperately (!!) need to be able to advise Person C (the approver) that there is a request they need to approve. I would also like to advise Person B (the user) that the issue has been raised on their behalf (given they are the reporter, but they are not the one who physically logged the issue). Email notifications are working for our Jira Software projects, which runs in the same Jira service instance.If a watcher is added (Person D), and this person is different to all other people currently listed on the ticket, they received a notification when a new comment was added to the ticket (which is correct as "All Watchers" are set up to be notified when an Issue is Commented).Person does not get notified of their own changes Note: In the scenario outlined above, Person C has no knowledge of the issue being raised, and consequently I'm not sure what is causing this particular status to occur?.Person received notifications for the 'Issue Created' event.Notification Helper (in project settings) shows the following same two items under 'status' for persons A, B & C:.Who can customers share requests with?: "Any customer or organization, by searching in this project".Who can raise requests?: Customers who have an account on this Jira site.There is a request type, customer status and channel all listed under the "service desk request' section.Person B and Person C are correctly listed in the created Jira ticket as the 'reporter' and 'approvals' fields respectively.I have checked and confirmed the following: This person does not have a service desk licence, but they are listed in the Directory. Person C = The nominated approvers of the issue.the person notifying the service desk of the issue). Person B = The user who the request is raised on behalf of (ie.Person A = Agent taking the call and logging the request on the portal on behalf of the user (they are not using the 'create' button - they are using the customer portal link).The following people were involved in the ticket, so I am expecting Person B & C to receive an email. When the portal is used to raise a new request, no-one is receiving an email notification. The notification scheme being used for the event of "Issue Created" comprises the following notifications : We are in the process of implementing Jira Service Desk (using Jira Server). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |