Gezim Shehu [Communardo] Community Champion

Hi David, Exactly the answers I was looking for. We always work with 3 parallel environments (at least) and Atlassian applications are no different. We have a dev env, staging/test env and prod so we can easily test the one jump upgrade in dev first. Glad to hear the new UI isn't present in server. I opened a trial cloud…

I See. Sounds interesting :) Thanks for the details.

Hi Nic, Do you mean that posts containing code blocks are likely to be marked?

and the guy keeps commenting but I can't access it.

I was also following someone's else question, and some weird notifications kept coming but no updates were made on the post. Next thing I know that was marked as spam.

This is if you are running Data Center, which at 3.4 I think it wasn't available yet.

I'm not sure about your case, as if even the license is valid, 3.4 has reached EOL way back ago. In theory a zero downtime upgrade of a non data center product would consist of building a parallel environment and switching IP/ports after the migration is done.

Agree. And the project variable can easily be configured using Field Contexts.

I think he doesn't mean to have it configured in a default field, but auto populating it. I don't know what the benefit is though.

One different approach might be using Insight as an asset repository and adding 2 insight fields, the 2nd being depended on the first. Object would be linked, i.e countries are linked to the state.

Well this add-on is not available for cloud, so you have to look at other options. Either search for a similar add-on or use ScriptRunner (with which you could easily implement a scripted field to calculate the time in status)

Are you on cloud? It's only available for Server.

I use Page Properties too for this kind of organization. I.e Procedures, properties, approvers, modules etc. and organize it in a overview page

Nice :)

Maybe someone else can hop in and help?

Do you have access in the logs? I really can't figure this out as I am not familiar with it and no log details make it difficult.

Is this a built in function for cloud? I currently have access to Server only and this is not an out of the box plugin. Mostly use Email this issue, or ScriptRunner's email PF.

I think it might be doable. Upon moving an issue, issue key is changed and this information is saved in issue change history. Now this is certainly searchable by querying the database. I think it can also be searched via Script.

I understand, but is it necessary, as this is a transition pointing to that status, so I don't think it's valid to add it as a condition. Can you try removing the condition? 

May I ask which is the scope of putting JQL condition into this?

Hi, Which are your assets? Meaning any scripting add-ons installed, such as ScriptRunner? In case you don't have any, you could also try the free one, Issue History Collecter/Stats here: https://marketplace.atlassian.com/plugins/ru.andreymarkelov.atlas.plugins.datacollector/server/overview It shows statistics in an issue…

In case you are asking for dropdown filters in boards, as your question I think it's actually already solved from Tarun's answer, but maybe you wrote it wrong. There used to be a feature like this back in the day, when JIRA software wasn't a thing, instead JIRA agile. It got removed, but one add-on can bring this back.…

Quick filters as a drop down? Can you post a screenshot.

Hi, Can you post some print screen of how you have the PF configured? Cheers

Hi, -Do you mean you want to add a new (non-existing) custom field on create issue ? If that's the case, it's doable via scripting, but surely strongly not the way to go. -In case you mean you already have a custom field configured, but not showing up in the Create Issue Screen, then check this link. It should provide…

Question: Do you use Insight? If yes,we have setup some SLA configuration based on objects attributes. -Think of them as groups. -In your case, you could have customers as objects (referring to JIRA User) and some groups, let's say SLA Group 1, and the customer would have an attribute called "SLA Group" which would point…

As far as I know, renewing your license will also include the cost of the period you were off maintenance.

I don't know any simple method to integrate a pop-up warning like that, but I can suggest a couple of ways of doing this. 1-Have 2 transitions to the same status, 1 containing a validation, the other one not containing a validation. 2-First transition should have a scripted condition to run a JQL query for assignee = new…

Not related to your question, but I would recommend updating Postgres version to at least 9.5. 9.2 support is deprecated on later JIRA Versions (though it doesn't mean necessarily it won't work) 

haahahha funny comments