Global counter for database migrations

Question

Hello again, community! I've searched some info but can not figure out how to create a custom parameter/filed for project to count migrations for database.

Situation:
We are using migrations and numbering them, i.e. I am working on issue PROJ-44 and I need to add a table to our db, so I am writing migration_68.sh and increase our global MIGRATION_COUNTER from 68 to 69. This counter informs other developers to use counter 70 for their future migrations. It is really usefull for us, because we just use migrate_all.sh, which applies all our migrations. 
But I can not figure out how to create custom global counter for this in a project, any ideas?

Thanks a lot!

Alvaro Aranda · Answer

Hi @Sergey Turkin,

I'm Álvaro from the DEISER's Apps team. We have created Profields to empower the way you work with projects in Jira.

It seems that you need one of these kind of project-level fields: number, cummulative or script. With Profields you will be able to create every of them.

If you want us to help you on configuring this, you can create a ticket on our Jira for Support here and we will be glad to help you. Also, we can schedule a demo to show you how Profields works, the possibilities you have with it and different use cases.

I hope you can build what you need with Profields.

Cheers.

Andy Heinzer · Answer

Hi Sergey,

If I understand your request here, you are not looking for a custom field that exists on an issue level, but rather some field that exists on a project and can be viewed, accessed, or just relating to all the issues of that project.

With just native Jira, this is not something you can currently do.  The custom fields in Jira are bound to specific issues in Jira.  There is no way to create a custom field that only applies to a project, and not to specific issues in said project.  There is a feature request for this in JRASERVER-1991.  From that most recent update from 28/Feb/2018:

While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

There are several third party add-ons that solve many of the use cases mentioned here:

* Profields
* JIRA Metadata Plugin
* JIRA Project Specific Select Field.

Perhaps one of these plugins could help you to implement your specific use case here.

I hope this helps.

Andy