サインイン
はじめてのオートメーションをわずか数分で作成できます。Studio Web を試す →
Jira
作成者: UiPath
1
アクティビティ
6.1k
could not install the package. Studio log:
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
, HResult -2147024894
06:37:24.4749 => [ERROR] [UiPath.Studio.Shared.Logging.OutputLogger] [17] Cannot load assembly: C:\Users\\.nuget\packages\atlassian.sdk/12.1.1\lib/net452/Atlassian.Jira.dll : System.TypeLoadException: Method 'get_RootElement' in type 'Atlassian.Jira.Remote.RestSharpJsonSerializer' from assembly 'Atlassian.Jira, Version=12.1.1.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.
at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
at System.Reflection.RuntimeAssembly.GetExportedTypes()
at UiPath.Studio.Plugin.Workflow.Services.AssemblyContainer.AddAssemblyInternal(Assembly assembly, String path)
at UiPath.Studio.Plugin.Workflow.Services.AssemblyContainer.c__DisplayClass9_0.b__0(Tuple`2 range)
06:37:24.4759 => [ERROR] [UiPath.Studio.Shared.Logging.OutputLogger] [17] Cannot load assembly: C:\Users\\.nuget\packages\uipath.jira.activities/2.2.0\lib/net461/UiPath.Jira.dll : System.TypeLoadException: Could not load type 'RestSharp.Serialization.IRestSerializer' from assembly 'RestSharp, Version=106.3.1.0, Culture=neutral, PublicKeyToken=598062e77f915f75'.
at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
at System.Reflection.RuntimeAssembly.GetExportedTypes()
at UiPath.Studio.Plugin.Workflow.Services.AssemblyContainer.AddAssemblyInternal(Assembly assembly, String path)
at UiPath.Studio.Plugin.Workflow.Services.AssemblyContainer.c__DisplayClass9_0.b__0(Tuple`2 range)
Hi - can you please confirm the version of Studio and the activity pack you are using?
Hi Paul - of course can do share. Could you please provide me with your email address or a way to share the log files? Thanks again, for the prompt response!
The best bet is to post a thread to https://forum.uipath.com/ as it makes it easier to have a conversation and share files.
The new preview package is unable to install on the Studio 2019.10.4 version, stating that the package could not be installed. It gives me errors with Atlassian.SDK implementation, but if I do the same on the new Studio 2020.4, I don't get the same errors. Any help would be greatly appreciated.
Hi Ravin - can you please send the error log to us for review?
This preview package has a dependency of UiPath.Platform.20.4.0 but the Compatibility listed states it will work with UiPath Studio 2019.10.4+. Will it work with Enterprise Orchestrator 2019.10?
Hi Scott, there is no dependency with orchestrator to run the activity. The dependency is strictly for UiPath Studio, which you'll need 2019.10.4 or later.
Hello Paul. Does the activity package support the JIRA SERVER v 7.0.0 (On-Prem) instance?
Some of the activities will work with the on-prem instance, however other activities are using the REST framework (vs. the SDK, as not all the functionality we wanted to provide was in the SDK), and the REST framework will only work with Cloud (per Jira). I'll update the documentation NLT tomorrow to ensure this is spelled out in greater detail.
How to identify the additional fields details and how to add those fields into the create issue activity.
Hi Suchita, this is done using the ID of the custom field. We are looking at enabling the use of the custom field name in the next release. I've updated the docs at https://docs-backend.uipath.com/marketplace/docs/jira-create-issue to illustrate this. Please do let me know if this doesn't make sense.
技術情報
バージョン
2.4.5更新日
2025年1月23日対応製品
Studio: 22.10+
認定
ゴールド 認定済み
サポート
リンク: https://www.uipath.com/company/contact-us/contact-technical-supportUiPath Standard Support, see your Service Agreement
