Record’s (row’s) number

[Kamal H_ SAGER]

How can we get a field for the records ( rows) numbers in JIRA? 

[Nic Brough -Adaptavist- · Accepted solution]

This would be utterly useless to you, as the number would have to change in almost every report you would run.

If you mean you want a numeric id for an issue, you can get one - the issue id in the database is numeric and unique, but it is sorted in creation order, can't be searched for, not sequential, and would not let you link to it.

Where do you want to see a "row number", and of what use would it be?

[Kamal H_ SAGER]

Thank you Nic, I did fix this issue by using Tableau Prep, this field will be used as a numerical rank.  

[Nic Brough -Adaptavist-]

So your Tableau reports are now wrong?

[Kamal H_ SAGER]

No, they are not wrong but I did add this row number to the JIRA database in Tableau Prep, all the reports now working and fully automated. 

[Nic Brough -Adaptavist-]

They almost certainly are wrong.  But you've never explained exactly what the row number means to you.  Where do you think you want to see this row number?  Why would it not change if you changed the sort order of the issues, or looked at a different report?  Row 123 in the issue navigator is rarely going to be row 123 in the backlog for example.

Your row numbers in your Tableau report might look right in one case, but they're utterly useless outside that case.

[Kamal H_ SAGER]

Think about this, how can we get two levels ( nested) of issue ranking let’s say on enterprise level and on project level without having a row number to associate with? This was my basic issue how to get a JIRA field  that reflects the row number which is also the rank of the issue on the enterprise level then I did create the sub ranking in Tableau. Now everything is working correctly and the row number is not changing when doing any sorting. 

[Nic Brough -Adaptavist-]

Ah, ok, so your "row number" is a rank.  That's fine, but you now have the problem that it will be overriding all the ranking in Jira, making the rank in Jira pointless, as well as only being valid for one backlog at a time.

[Kamal H_ SAGER]

I think this is the only way to get issues ranking in numerical form. I do agree it’s  valid for one backlog at a time when we pulling the data which is fine with the reporting requirements with daily refresh schedule. 

[Nic Brough -Adaptavist-]

Yes, your row numbers may be fine in one very specific place, but they're useless everywhere else, because you're going to get different numbers.  Similarly, they're going to be obsolete as soon as you extract them, because things change.

[Mohamed Adel]

Hi @Kamal H_ SAGER  

Can you elaborate more please what the exact field you need ? 

Regards

Mohamed

[Kamal H_ SAGER]

Thank you Mohamed for the reply, simply I need a field with integer data type that represents the record ( i.e. row) number for each issue key. I am working on doing two level of ranking associated with issue key hence I need that field in the exported JIRA data. 

[Mohamed Adel]

You can create an integer custom field where you can fill it with the Issue ID, using the following smart value :{{issue.id}} on Issue Create Trigger

I hope this can fix your problem 

[Kamal H_ SAGER]

The field should be like index number for the issues (1,2,3,4….etc) not the issue Id itself!