You can now synchronize sub-tasks with their parent issue and stories with their Epic. You can also copy the value from other fields of the issue and use smart-values. This is now trivial to do with Automation for Jira.Ī great example of this is when QA rejects a story: There are quite a few use-cases where you want to pass issues between users and have the assignee go back and forth as well. If you want to gamble a little - we also have the ability to assign it to a random user… You create the list of users manually, and each time the rule runs it assigns the issue to the next user. To make sure everyone has their turn, we now have Round-robin assigning. We then fall back to a balanced workload.Ī good team takes turns to do “those” scheduled tasks weekly releases, translations, paying bills… To maximize this, we can now assign tickets to the assignee of the last ticket that the reporter raised (or even more sophisticated use-cases). Part of legendary service is to build relationships with your customers and giving each customer continuity between interactions. This search can be customized to suit your needs: Now we can simply use a rule so that whenever an issue is created, it searches for a member of our team with the least amount of open tickets. Previously we would have to look at the current open issues and manually count how many issues were assigned to everyone doing support and then assign it to the developer with the least amount of tickets. Part of this is ensuring that we share the workload so we can respond as quickly and effectively as possible. Balanced workload assigningĪt Automation for Jira, we try to offer the legendary support that we learned at Atlassian and we use lots of rules on top of Jira Service Desk to help us achieve that. Let's look at some of these in more depth. … As I said, customers came up with a lot of use-cases. look back in the issue history at previous assignees or users who have commented.copy assignee from a related issue or JQL query. ![]() As such, we scored smarts popularity level to be Limited. assign issues in a round-robin fashion to a defined list of users The npm package smarts receives a total of 276 downloads a week.assign issues based on current workload.Never run out and save up to 50 on ink or toner Get ink or toner, plus hassle-free delivery and recycling, all starting at 0.99 a month with HP Instant Ink. Install the HP Smart app on all your devices and save time for what matters. How can Automation for Jira assign issues to users? HP Smart Stay productive and organized with HP Smart Print, scan, and share to your HP printer anytime, anywhere. It will be assigned conditionally using the smarts of Automation for Jira. A common request we kept hearing was to be able to assign issues in a smart way.īy ‘smart’ we simply mean Jira admins want to ensure the right person is aware of an issue and accountable for it. We love talking to customers about how they are using Automation for Jira Server and what features we can build to make their lives better.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |