Currently, the Smartsheet/Jira Connector is not populating the Parent Link, as Jira moved all Epic Link into Parent Link. With Parent Link, this allows user to be able to calculate the percentage of the completion of the Epic, so anything and everything can fit under it. There is a bug or no support as smartsheet should be able to dump everything from JIRA into Smartsheet, but this one is not working.
Any updates on this?
This is definitely an issue now that the Epic Link is officially retired since 2/13. This is now causing errors in our Jira-SS connector. It's as if on the SS side, you are still using the Epic Link and have not updated the Parent filter.
The Epic Link has a drop down of all of our Epics/Parents.
The Parent filter is a text box. This should map to the Epic numbers, as the Epic Link filter did previously. Please fix this!
@Genevieve P. I got notification you left a comment and now I can't find it. I hope you have good news that this has been fixed?
We have released the Parent Field within the Smartsheet Jira Connector! You can see more details on the release here.
For Jira on-prem workflows, you can now select the Parent field (bi-directional) in addition to the Epic Link (bi-directional) and Parent Link (uni-directional) fields within the Jira Connector. For Jira Cloud workflows, as the Epic Link and Parent Link fields have been removed from Jira Cloud, these fields have been removed from the Jira Connector and the Parent field has been added to the workflow builder.
Danielle W.
Product Marketing
Smartsheet
@Danielle Wilson Although the Parent Link is available in the connection fields, I'm still having errors due the Filter JIRA issues. When I select the filter "Parent" it is not a drop-down like the filter "Epic Link" which has options for all the Parent/Epic Links. Because of this, my SS row is not creating a card in Jira. Same screenshots as above. Has this been updated?
Just in case anyone else checks here - this issue has been resolved!
Danielle W.
Product Marketing
Smartsheet
@ How was this solved? If I create tasks and subtasks in SS and push to Jira, Jira will not identify the parent. Then, when the issue key pushes back to SS it removes it in SS because Jira pushed back a blank field.
We do not want to manually type in the parent in SS or Jira, that will defeat the purpose of the automation. The Jira user won't know the parent of a subtask, etc without going into SS and the SS user won't know the parent without going into Jira.
@Angie Hatfield did your team link the task and subtask to the parent? Cause it seem like your team is not linking it from JIRA. The team will need to link the task and subtask first then it won't be blank. Doing it from SS to Jira will not work cause Jira should be the source of truth if you are using the automation.
If a Project Manager pushes a new project into Jira, either they will need to go in and manually link every task and subtask or the Jira team will need to do it. The Jira team won't know what the parent is. It will just be a task sitting there. Also, we've run across that if a subtask doesn't have the parent linked in SS before it goes to Jira, then it's not landing in Jira at all.
With the indenting in SS, there should be a way to identify who the parent is.
@Angie Hatfield if you are using this connector, Jira should be the source of truth. Then you should have automation in Jira that auto tie the task subtask story under the same parent/epic. This bug was found where I couldn’t export out the parent into SS. Cause I was trying to build a dashboard in SS to show the status of the epic/parent.
Thanks @Allen T , good to know. That is helpful to me!