Jira - Revision history

Jkuehlthau: /* Connector */

2024-02-21T20:44:46Z

Connector

← Older revision		Revision as of 20:44, 21 February 2024
Line 1:		Line 1:
	=Connector=		=Connector=
	The Jira connector is fairly standard. It asks for your username, password and URL. Your URL will be something like: https://starfishetl.atlassian.net. Your "password" may not be your password. In some, or all, accounts, you must supply an API key as your password. To generate an API key, as of this writing, open the "Settings" gear icon -> Atlassian Account Settings -> Security -> Create and manage API tokens. Create a Token for Starfish to use and put that into the "password" field.		The Jira connector is fairly standard. It asks for your username, password and URL. Your URL will be something like: https://starfishetl.atlassian.net. Your "password" may not be your password. In some, or all, accounts, you must supply an API key as your password. To generate an API key, as of this writing, open the "Settings" gear icon -> Atlassian Account Settings -> Security -> Create and manage API tokens. Create a Token for Starfish to use and put that into the "password" field. You can also use the "Authorize" button.

	The connector is based on ~~code~~ from CData. See documentation here: https://cdn.cdata.com/help/~~BJG~~/ado/~~pg_startedintro.htm~~.		The connector is based on a DLL from CData. See documentation here: https://cdn.cdata.com/help/BJJ/ado/.

	=Origin Filters=		=Origin Filters=

Jkuehlthau: /* Date Time */

2022-10-27T15:34:26Z

Date Time

← Older revision		Revision as of 15:34, 27 October 2022
Line 17:		Line 17:
	</syntaxhighlight>		</syntaxhighlight>
	Please note that Jira Query Language does NOT support seconds. See this post: https://community.atlassian.com/t5/Jira-questions/Jira-API-JQL-Datetime-Format-Doesn-t-Support-Seconds-and/qaq-p/1476275.		Please note that Jira Query Language does NOT support seconds. See this post: https://community.atlassian.com/t5/Jira-questions/Jira-API-JQL-Datetime-Format-Doesn-t-Support-Seconds-and/qaq-p/1476275.
	Even though seconds are not supported, it seems to filter by the seconds equaling 00. This as the effect of making > and >= behave the same. Because you are saying > ...:00 or >= ...:00. I suppose it might make a difference if the date you are filtering on happened at exactly ...:00. I'm going to stick with >= just to be sure.		Even though seconds are not supported, it seems to filter by the seconds equaling 00. This has the effect of making > and >= behave the same. Because you are saying > ...:00 or >= ...:00. I suppose it might make a difference if the date you are filtering on happened at exactly ...:00. I'm going to stick with >= just to be sure.

	=Sorting=		=Sorting=

Jkuehlthau: /* Origin Filters */

2021-09-15T21:28:41Z

Origin Filters

← Older revision		Revision as of 21:28, 15 September 2021
Line 5:		Line 5:

	=Origin Filters=		=Origin Filters=
			When Querying Issues, it is supposed to use Jira Query Language: https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-14. It seems to follow these rules, but some trial and error may be required. Also note that sometimes, fields queried on do not seem to match what is returned. For example, when looking at a records returned values, you may see "fields.updated". To filter on that field, you have to use "updatedDate". I'm not sure how to find where or why this occurs. I used Google.
	==Custom Fields==		==Custom Fields==
	To filter by a custom field, use cf[FIELDID]. Example:		To filter by a custom field, use cf[FIELDID]. Example:

Jkuehlthau: /* Origin Filters */

2021-09-15T21:25:26Z

Origin Filters

← Older revision		Revision as of 21:25, 15 September 2021
Line 5:		Line 5:

	=Origin Filters=		=Origin Filters=
			==Custom Fields==
			To filter by a custom field, use cf[FIELDID]. Example:
			<syntaxhighlight lang="csharp">
			cf[10100]~'47'
			</syntaxhighlight>
	==Date Time==		==Date Time==
	To filter by Date/Time, Use:		To filter by Date/Time, Use:

Jkuehlthau: /* Sorting */

2021-09-15T21:22:53Z

Sorting

← Older revision		Revision as of 21:22, 15 September 2021
Line 14:		Line 14:

	=Sorting=		=Sorting=
	Append "order by FIELD ASC/DESC" to your Criteria		Append "order by FIELD ASC/DESC" to your Criteria. Example:
	<syntaxhighlight lang="csharp">		<syntaxhighlight lang="csharp">
	order by updated ASC		order by updated ASC

Jkuehlthau: /* Origin Filters */

2021-09-15T21:22:09Z

Origin Filters

← Older revision		Revision as of 21:22, 15 September 2021
Line 11:		Line 11:
	</syntaxhighlight>		</syntaxhighlight>
	Please note that Jira Query Language does NOT support seconds. See this post: https://community.atlassian.com/t5/Jira-questions/Jira-API-JQL-Datetime-Format-Doesn-t-Support-Seconds-and/qaq-p/1476275.		Please note that Jira Query Language does NOT support seconds. See this post: https://community.atlassian.com/t5/Jira-questions/Jira-API-JQL-Datetime-Format-Doesn-t-Support-Seconds-and/qaq-p/1476275.
			Even though seconds are not supported, it seems to filter by the seconds equaling 00. This as the effect of making > and >= behave the same. Because you are saying > ...:00 or >= ...:00. I suppose it might make a difference if the date you are filtering on happened at exactly ...:00. I'm going to stick with >= just to be sure.

	=Sorting=		=Sorting=

Jkuehlthau: /* Connector */

2021-09-15T20:55:20Z

Connector

← Older revision		Revision as of 20:55, 15 September 2021
Line 1:		Line 1:
	=Connector=		=Connector=
	The Jira connector is fairly standard. It asks for your username, password and URL. Your URL will be something like: https://starfishetl.atlassian.net. Your "password" may not be your password. In some, or all, accounts, you must supply an API key as your password. To generate an API key, as of this writing, open the "Settings" gear icon -> Atlassian Account Settings -> Security -> Create and manage API tokens. Create a Token for Starfish to use and put that into the "password" field.		The Jira connector is fairly standard. It asks for your username, password and URL. Your URL will be something like: https://starfishetl.atlassian.net. Your "password" may not be your password. In some, or all, accounts, you must supply an API key as your password. To generate an API key, as of this writing, open the "Settings" gear icon -> Atlassian Account Settings -> Security -> Create and manage API tokens. Create a Token for Starfish to use and put that into the "password" field.

			The connector is based on code from CData. See documentation here: https://cdn.cdata.com/help/BJG/ado/pg_startedintro.htm.

	=Origin Filters=		=Origin Filters=

Jkuehlthau: /* Date Time */

2021-09-15T20:53:57Z

Date Time

← Older revision		Revision as of 20:53, 15 September 2021
Line 8:		Line 8:
	updatedDate>="2021-08-12 10:40"		updatedDate>="2021-08-12 10:40"
	</syntaxhighlight>		</syntaxhighlight>
			Please note that Jira Query Language does NOT support seconds. See this post: https://community.atlassian.com/t5/Jira-questions/Jira-API-JQL-Datetime-Format-Doesn-t-Support-Seconds-and/qaq-p/1476275.

	=Sorting=		=Sorting=

Jkuehlthau at 20:53, 15 September 2021

2021-09-15T20:53:00Z

@@ Line 1: / Line 1: @@
 =Connector=
 The Jira connector is fairly standard.  It asks for your username, password and URL.  Your URL will be something like: https://starfishetl.atlassian.net.  Your "password" may not be your password.  In some, or all, accounts, you must supply an API key as your password.  To generate an API key, as of this writing, open the "Settings" gear icon -> Atlassian Account Settings -> Security -> Create and manage API tokens.  Create a Token for Starfish to use and put that into the "password" field.
 =Inserting a File=

Jkuehlthau: /* Inserting a File */

2021-08-12T11:42:28Z

Inserting a File

← Older revision		Revision as of 11:42, 12 August 2021
Line 3:		Line 3:

	=Inserting a File=		=Inserting a File=
	To insert a file, create an Insert Stage for the attachment table.		To insert a file, create an Insert Stage for the attachment table. Pass the file to the attachment byte[] field. In this case, I was reading from SugarCRM, so I did not need to convert the object returned by the Smart Lookup.
	<syntaxhighlight lang="csharp">		<syntaxhighlight lang="csharp">
	object ScriptedField()		object ScriptedField()