Is it possible to route tickets to a specific group depending on form chosen by end-user with Zendesk? - zendesk

: Is there a way to have tickets submitted to a specific group (not individual) depending on the form the end-user chooses at the help center?
For instance if the end-user was to choose form A, (out of possible forms A, B, and C) would it be possible on submit, for the ticket to be automatically routed to fall under a specific group in which the task could then be delegated to a specific agent? While forms B and C would route their tickets to their own respective groups?
Is this possible, or does an agent/manager/admin HAVE to assign a ticket to a group manually through the webapp?

SOLVED THE ISSUE: This is possible by using triggers.

I would replace the ticket is new with ticket is created so it will do that routing once on ticket creation.

Related

Jira: Team management for a ticket

My boss come with a very unique requirement, below is the explanation.
Imagine there is 10 user for a particular project team.
And the work flow is like
Documenting -> Review -> Publish
Now, the requirement is like below.
If I create Ticket with Summary "Version 1.0 Documents" with the above explained workflow, then it should also allow us facility to manager for user regarding each state of workflow like
Documenting assign to User A
Review Assign to User B
Publish Assign to User C
Note: I know I can assign ticket to individual user while changing state, but I want something pre-planned so as soon as I change status of ticket it will automatically assign to user.
I know I can do this using post action of transaction but what I want is, the assignee should be specified at creation of ticket as the same workflow going to use by many project and ticket, and every project will have different team
So , I need something add-on which allow me to manage team for each ticket.
Also, User C should be able to see his/her upcoming work if ticket is in any previous state i,e Documenting or review.
I suggest you should create account role for this and group to each department/team for their flow. you can use account role for separating their works then the department/team is useful for which members/users can see the particular issue/ticket. we already build something like this we have 3 account roles each ticket so i can say this is possible. if you still have question just let me know thanks.

Primefaces push

I would like to use 'primefaces push' in my web application to receive notifications.
I would like that a user could receive notifications depending on the groups he belongs to. Every user can belong to several groups, for example:
User X belongs to Group A and B.
User Y begong to Group A, C and D.
User Z belong to Group B and C.
When a user is logged in the web application then this user should subscribe to these notification groups.
My question is how many 'socket' I must create for a user.
<p:socket onMessage="handleMessage" channel="/groupX" />
For example, if a user belongs to two groups, should I dynamically create two socket in the JSF page? Could I just create one socket and use it to receive notifications from different groups?
Thanks
Assuming they are not subsets of one another, you cannot use one generic socket (one channel). Depending on the number of logged in users and/or the number of groups and/or the number of groups a user is a member of, I can see an additional possible solution (besides creating a socket for each group as you already mentioned)
Create a user specific channel for each user and on the server maintain a HashMap with the group name and a list of logged in users that belong to that group. When a message needs to be send to one group, iterate over the list and send it to each individual user

How to dynamically populate Jira custom fields?

I'm new to the Jira admin side of things after having used it in a previous company as an end-user for several years. We are using the standard Jira workflow. The scenario I'm struggling with is the following. I'm attempting to match some of the functionality of our old-proprietary issue database. Right now I'm using many of the standard Jira fields, with only two new custom fields (both single Select Lists populated manually by me):
1) Customer = customer name who sent the new issue email to our support team
2) Customer Contact = the main customer contact, currently populated by the custom list
I created these two custom fields because we have external customers who call or email issues they have using our hosted software. Currently our system creates a simple new issue when a customer sends an email to our support email account. Our support team then goes in and cleans up the data and makes sure that all the required Jira fields have data, the comments are good, reproducible steps, etc. (Currently we do not strip out the customer domain name to auto-populate the Customer custom field, but I might try doing that soon.)
Our support team is asking that I add the following two new customer fields:
3) Customer phone number
4) Customer connection / login info
What I would like to implement is a system that goes something like this:
Customer name gets inputted (either automatically by grabbing domain name of customer email address or manually by our support team) into the Customer custom field. Customer name selected should be "pushed" into the Customer Contact Select List to help sub-select values for that particular customer.
The Customer Contact Select list should be "smart" or dynamic in that some pre-processing is done where the Customer name is grabbed so that it doesn't show ALL customers contacts for the tech support person to select, it just shows them the customer contacts for the customer that was selected.
Along with the filtered customer contacts, I would want to only see the Customer phone number for the contact that was populated in the Customer Contact select list.
And finally I would want to see the Customer connection information for the particular Customer that was selected.I've done this type of smart combo boxes in the past when I created Java / Database applications, so I have a feeling that this is possible in Jira. I'm just looking for the easiest way to implement this. It seems like there might be some external plugins that might help do this (ex. the values for the Custom fields are stored in a database table so they can be queried and the proper filtered result sets can be populated into the select lists.), or maybe using post functions (update issue), etc. But before I spent more effort investigating, I know this sort of thing has to be somewhere common and wanted to ask the Jira admin experts what the best practice would be for this type of functionality in custom fields. Please share your experience with how to solve this type of scenario. Thanks in advance!
Here is the way that tells how to import multiple options at once. Probably that would help u.
https://answers.atlassian.com/questions/92385/importing-project-from-another-jira-instance-how-do-we-mass-import-custom-field-multi-select-options?page=1#92622
EDIT
and here is the complete code to update another select list using new select list.
How to add new values to select list field in jira dynamically or using plug-in

TFS Alert if change was made by users in a certain TFS Group / AD Group?

I am trying to set up an alert that will send me an email when someone who has Work Item Only View access creates/changes a Work Item.
I can create a query which returns me a list of Work Items which were created by WIOV users, by using 'Created By (In Group) "[TEAM FOUNDATION]\Work Item Only View Users"', or alternatively the AD Group which I created which controls which users have WIOV access.
But there does not appear to be an "In Group" operator in the Alerts Explorer.
Is there any other way to achieve this?
You can't check in an alert rule if a given user is a member of a group, so you won't be able to do that this way.
Maybe the fallback would be to ask to your wiov users to create the work items and not assigning them to someone (let the assigned to field empty), then you could be able to create the alert that triggers when such Work Item is create.
Note: you may have to change the definition of the Work Item to allow an empty "Assigned to" (depending of the Process Template you use).
I know I'm late to the party but you could do this a different way. Create a new project team in TFS and add your specific users/AD groups to that project team. Then, set the alert just for that specific project team.

How to handle pre-registered users and avoid duplication in rails

I am trying to figure out the best way to handle this situation:
User signs up -> creates a group -> adds users to the group
Added user comes to the site -> signs up -> sets up a different group
There are two classes of "user" here: registered(who log into the web-app) and non-registered(who can interact with the app purely via email due to them being added to a group). I have a boolean field for "registered".
A user that comes to the site and creates a group is "registered". A user that is just added to a group is not.
What I want to do is run a check when a new user is created to see if they are already in our database and in a non-registered state. Their email must be unique so essentially new users that are already a member of another group need their data updating rather than a creation of new users.
I also thought about separating my db schema into Users and Members then upgrading Members to Users if they come to the site and sign up, instead of just integrating with the app over email.
What do you guys think?
(Thanks in advance.)
I wouldn't have separate tables if the only difference is a state/role; just see if they're already in the system, and if they are, flip their state.

Resources