You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I've recently started using the Smartsheet connector for Jira and writing a use case. Has anyone else used this? I'd be interested in hearing information and experience if anyone has anything to share.
@Lydia M - "tried this--didn't work, tried that--didn't work" is exactly how it goes! I've used it extensively. Here are some tips n' tricks...
1. You cannot update Assignee via Smartsheet unless the user has their account settings configured appropriately.
2. "Save as new" is your friend. Every so often, save a copy of your sheet since it's easy to overwrite data when troubleshooting your connector.
3. End date cannot (mostly) be synched. If your Smartsheet plan has dependencies enabled, you can only sync End date (or whatever your plan's end date is) from Jira -> Smartsheet.
4. If you close a ticket in Jira, and your connector filter rules say "don't synch items that are closed," then it won't update Smartsheet with the correct Jira status.
5. Smartsheet does not understand Jira hierarchy beyond Epic. So, if you have a Jira hierarchy defined as Initiative -> Epic -> Standard Issue -> Sub-task, then Smartsheet won't know how to cleanly handle the Initiatives (there's a trick, but it's not pretty).
6. If you specify a Smartsheet hierarchy other than Epic -> Standard issue -> Sub-task AND you want to be able to create new issues from Smartsheet, then the PRIMARY Smartsheet column MUST be Key (Jira key/issue ID).
7. Smartsheet connector does not support two-way synch of cascading select lists.
8. You need to make sure the fields you want to connect are visible on the Create and Edit Jira screens.
9. Although it's allowed, I would absolutely not connect two sheets to the same project/set of issues. You'll get each one constantly updating with the other and it will make you crazy.
10. Name your Smartsheet columns with something that indicates if it's synched so users know. For example, instead of "Summary" name it "Summary ->" for fields that update from Jira to Smartsheet, and name it "Summary <-" for fields that update from Smartsheet to Jira, and name it "Summary <->" for fields that update in both directions.
The Jira connector does work, but can be a pain to use, as you can see from other people's comments here too.
I also don't remember seeing any enhancements or roadmaps for the Connector itself, so not sure how committed Smartsheet is on this tool.
If you are not tied to Smartsheet, explore the Google Sheets <> Jira integration too.
Lol.. Hi Mike. You are being modest. All I did was introduce it to you, and away you ran with it.
BTW.. we learnt some hard lessons... you CANNOT assign or make somebody else the owner of a Connector workflow, and they have to be recreated from scratch. Was not fun doing those :-(
We opted not to get the Smartsheet connector (largely due to cost) and also because we have Workato, an awesome integration application that we use across the company for all sorts of integration. We're working right now to integrate Jira and Smartsheet using Workato so it's still in the early stages but so far it seems like it will work pretty well for us.
We use Boomi as our integration platform and that works really well. However, Jira & Smartsheet's API leave a lot to be desired (IMO). So the Connector handles our Use Case really well. However, the Connector does have several limitations; Like one sheet can only connect to 1 project. So if you have multiple Jira Projects to connect to, you'll need separate sheets with their own connection logic. This works well for us so that it forces our Professional Services team to ensure they are adding work to the Right sheet so the proper Dev team gets the work, Rather than everything going into a "Catch All" and asking Dev Operations to sort it all out.
I have found that while you can have a Smartsheet that connects to multiple Jira projects, you can only create one workflow/connector per Smartsheet.
For example, in my Smartsheet, I have Development issues syncing to DEV Jira project, AUDIO issues syncing to that Jira project, and QUALITY issues syncing to the QA Jira project. But I can only have one connector for that sheet.
We use it so that our Professional Services team can Add a Row of something that our Development team needs to do so it creates an issue for the Dev team to work and as they update their Progress, Status and estimated Delivery dates flow to Smartsheets to keep PS Updated so they can inform clients.
I do have a specific question regarding the connector. In a case where an issue is carried over to multiple sprints, I've found that the connector will only pull the latest sprint over on the Issue. So if Issue A was not completed on Sprint 1 or Sprint 2, but was completed on Sprint 3, Issue A in the Smartsheet is only associated with Sprint 3.
As a workaround, I'm recommending our team stops carrying issues to multiple sprints. Jira addresses this by advising users clone a story if no work was completed and they want to add it to the next sprint, or split it if some work was completed.
The problem comes in when a story is cloned. Orig story moves to the backlog and clone story moves to the next sprint. Orig story is not ever going to be worked on and we really don't want it in the backlog, we just want it reflected as Not Completed at the end of that Sprint. Any recommendations?
I have used the smartsheet connector to create reports for teammates to track progress on their requests that do not have access to Jira.
We receive requests from other divisions, but these teammates do not have access to Jira to track progress of these requests. I've created filters that provides the information that they (requester) are interested in, pull that filter into a smartsheet using the connector, and then save these reports in a sharable location. When the end user opens the smartsheet, the filter is triggered, giving them up to date information each time they open one of the reports. This keeps us from using up Jira seats for users who would only need read access, but still allows us to share important information with them regarding their requests.
We primarily use Smartsheet for project plans at my company, so at some point someone got this connector that Smartsheet offers.
It's been pretty good so far, but it has taken a bit to get it to work consistently. My use case is full of "tried this--didn't work, tried that--didn't work" lol!