Problems using dinamic query based on issuetype parameter - Kepler

[amandavarella]

I´m trying to do the following configuration

SELECT CLASSIFICACAO_SERVICO

FROM JIRA_SERVICOS_SUSTENTACAO_SNEP

WHERE TIPO_CONTRATO = 'GS'

and ISSUE_TYPE_ID = {issuetype}

If i replace the issuetype parameter with a valide issuetype id, I got the results I was expecting. But as I put it in the form of a parameter (depending on the selection of the issue by the user) I got nothing as a result. Does not return any error in the log. Any help on this?

 

[Alexandra Topoloaga · Accepted solution]

Hi, 

My bad - I haven't realized  that you are trying to use issue type id. The  issueType variable references to the issue type name (which is, also, the one that you see in the create/edit screens), not its id.

We don't provide (at least not yet) a way to reference the issue type id.

Alexandra

[amandavarella]

Thank you so much Alexandra! It had worked. It´s even simpler 

I suggest you to improve the documentation with this information. I couldn´t find, so I´ve tried in a way similar with the custom fields.

Thank you!

[Alexandra Topoloaga]

Thank you for your suggestion, I'll update it ASAP. :)

[amandavarella]

Hi Alexandra, my version is 

Version: 3.0.6

Vendor: Kepler Rominfo

Add-on key:com.keplerrominfo.jira.plugins.databasecf

[Alexandra Topoloaga]

That's weird; are you using the latest version of DBCF? 

[amandavarella]

No Alexandra. I'm trying to use on a create issue scree

[Alexandra Topoloaga]

Hi Amanda,

I'm guessing you're trying to use the script on an edit screen: it is the expected behavior - the stored value is used, so until the new value of the issue type is saved, the data base custom field won't get updated.

On the other hand, on create issue screen, should work just fine.

Hope this helps,
Alexandra