Jira Live-Search Validation

Hey ​@jmonckton - When using enterprise search a user will be able to see a list of available connectors that they can authenticate with

​@Kevin Mok do you happen to have the Enterprise Search package? I do not have the same view that you do have, as our organization does not have Enterprise Search

I see, I do since I work for Moveworks😆 - Are you expecting better documentation on our part for you to see the flow. Or what exactly are you looking for?

When users authenticate, they will be sent to jira to authenticate using SSO or their email based on your companies policies. Does that make sense? 

How can a user initiate the authentication? If a user was looking to use Jira Live-Search functionality, will they be prompted to authenticate within the Slack channel? When testing, it seems the only way we can validate/authenticate is by re-validating within the connector config? Pressing “View Details” and then “Re-Validate" sends a Slack message from our movement bot that lets us authorize. How would an end user receive the same message so they can authenticate?

Thank you for your assistance :)

Hi ​@jmonckton. I am a PM on the Search team. Apologies - you came across a documentation page for Jira live search which is not quite ready for launch. This page should not have been visible. 

However, I would love to learn about your use cases and what you would want to use Jira search for. Thanks! cc ​@Indrashis 

Hey ​@rraj - Would be happy to provide our use case for the jira integration:

• Our employees live and breathe in slack and context switching is an annoyance. the expectation here is that an employee could oauth into jira (if they have an account) through moveworks and that jira tickets become another area of knowledge returned to them. 
  • For example, say an employee asks moveworks slack bot “whats the latest on the deployment that happened last week?” moveworks would realize that they have jira connected and poll tickets that their account has access to, to build out a response that could include/reference jira tickets related to the deployment. 

Let me know if this doesn’t make sense, ideally we just want jira as a knowledge source, in addition to other areas such as confluence/google/etc, as ticket data can have useful information within it.