Assist App in Slack connected with JSM Portal

[Leo]

Hi!
We are testing right now how to connect Slack with Jira even more. The backgroud for this is that we know users tend to stay in Slack and prefer not to go to Jira for submitting request, this happens all the time so we were testing some solutions provided from Jira including the Vistual Agent (I'll post another question about it). 

So using the Assist app works really good, but we've encountered two issues:

1. Information from Assets fields aren't shown in Slack, please check the following images to see which one is the missing field in the Access Request form:
   
   
   1. 
      
      
   2. 
      
      
2. The other "issue" is more about how to make it possible for users to use the Assist app without having to type "/assist" in Slack. We thought on creating a Slack workflow but Jira Assist isn't available for that option. Although this question might be more for Slack, but it could be that you have some ideas around this. This is also because users don't like to type something like that command as they might considered inconveniant.

[Manoj Gangwar · Accepted solution]

Hi @Leo For the 1st question, asset fields are not supported in the slack chat. Please vote on the below suggestions.

https://jira.atlassian.com/browse/JSDCLOUD-13959

For 2nd question,

To use the Assist app in Slack without typing "/assist", you can create a virtual service agent channel. Here's how:

1. Go to the Slack channel you want to use.
2. Send a message in the channel with /add.
3. Select Add apps to this channel.
4. Search for Assist.
5. Select Add.
6. Choose Agent channel.
7. Select the Jira Service Management project you want to use.
8. Invite agents and admins to the channel by typing /invite. 

Once you've set up the virtual service agent channel, you can use emoji reactions or slash commands to turn any message into a trackable request. 

[Leo]

Thank you for your message. I went to the link and voted for the option. On regards of your answer to the second question, that unfortunately will not work as the Virtual Agent shows only one type of request from the portal and we have severals. I opened up another question related to this situation.