Jira Connector - No error, but Field changes do not synch back to Jira
We have three important fields we use to report on our jira issues. I'm trying to create an audit list, via a 2 way jira connector synch - to review a list of issues and easily be able to update these three fields. The feidls are:
1) Labels
2) Requestor
3) Epic Link
When I try to update 1) in smart sheet, I get the field is not on the edit screen error - OK, but Lables is not a field that is available to add to the edit screen - how do I change that?
When I update 2) - the sync runs (I can verify by editing the summary of the issue and that goes across) but the Requestor does not change in Jira. Furthermore, the 2way synch then quickly runs again and changes the Smart Sheet Requestor back to the original value...? Requestor field IS on the edit screen.
#3 works great.
TIA!
Best Answer
-
What type of field is the "Requestor" field? At this time multi-select picklist fields from Jira are supported unidirectionally (from Jira to Smartsheet, but not from Smartsheet to Jira). See this other Community Post, here.
If this wasn't the issue, you may want to reach out to Smartsheet Support with screen captures of your Jira workflow configuration, identifying each of the field types, and a screen capture of your sheet, identifying each of the column-types.
Cheers,
Genevieve
Answers
-
Ok, I've read more about adding fields to screens - so I can work with our admin to do that. But still confused about #2.
-
What type of field is the "Requestor" field? At this time multi-select picklist fields from Jira are supported unidirectionally (from Jira to Smartsheet, but not from Smartsheet to Jira). See this other Community Post, here.
If this wasn't the issue, you may want to reach out to Smartsheet Support with screen captures of your Jira workflow configuration, identifying each of the field types, and a screen capture of your sheet, identifying each of the column-types.
Cheers,
Genevieve
-
Thanks Genevieve -- yes, both Labels and Requestor fields are "lables" type of field -- which I was suspicious was the cause but I could find no reference in the docs as to what field types were supported.
