Nic Brough -Adaptavist- Expert

Get rid of it. It's slow (as in your performance is suffering), painful to use, and your humans are almost certainly getting it wrong. Are you sure they are selecting the right one from a list of 10,000? Are they genuinely useful? Are they all being used? There's a good reason many systems limit select list options to 55 -…

You are not contrarian at all! I would have said "rightly questioning" because I failed to explain the empty content scenario you asked about. I am sorry for that. Templates do not just cover content. They shape some of the metadata too. You can't apply a template to an empty page because there is already something in the…

Yep, Atlassian have not yet enabled the functions that would allow Scriptrunner to set security levels. But... you can do it with Automation. You could: * Trigger: Issue transitioned * Conditons: (whatever you need) * Action: Edit issue* Field: Security level -> <value>

Epics are different, they have two status. As issues, they have their own workflow, the same as any other issue type. But they also have an Epic Status, which is to-do, in-progress, done. This has nothing to do with the issue workflow, it's derived: * if there are no stories for the Epic, or none of the stories have moved…

My guess would be that description is hidden in the target project. But there's no way to be sure without looking at the issue history.

Are you trying to count the number of times someone uses a transition called "resolution rejected"?

Welcome to the Atlassian Community! The NPE on that line means that the "parent" variable contains a null, not the issue object that the function needs. So my guess would be that the parent issue the script is running against does not have an Epic link (or the code on the line "MutableIssue parent = ..." is wrong, although…

Welcome to the Atlassian Community! Either ask the admins of the Bitbucket system to do something about it, or report it to https://www.atlassian.com/trust/report-abuse

Welcome to the Atlassian Community! I think you are in the wrong place. I don't recognise any of that as being Atlassian related. If it is, then could you explain how? I suspect you may need to ask your admins, not an Atlassian community!

Welcome to the Atlassian Community! You probably don't want to do this. Your issue will look wrong if a project changes category.

That would work too, I went with custom fields because I'm more familiar with them.

Welcome to the Atlassian Community! You do not "add a template" to anything (except in Confluence, you add them to the global or space lists of templates). Templates are forms, molds, or patterns used to create a new thing. They shape the new thing and then have nothing else to do with it. So, in Confluence, you use a…

What does the documentation for the app say? (I do not have time to read new things that I'm not directly sing)

Welcome to the Atlassian Community! Please see https://jira.atlassian.com/browse/JSDSERVER-5847 - the recommended solution is not a botch with querydsl, but upgrading to a fixed version - 3.13.2 (or ideally, a supported version, bearing in mind there's only 10 months of support left for any version of Server)

Repeating the problem does not show that you have tried what I wrote. Please re-read my answer and try what I suggested.

There isn't anyone. It's gone away.

I can give you a bit more history - Community (on Khoros/Aurora) is the fourth incarnation of it. When I started looking at Atlassian stuff, I got a lot of help from mailing lists, chats, and then a Jive based forum. Like @Teodora V _Warsaw Dynamics_ the help I got there lead me to want to give something back. I will not…

Custom fields don't have that formatting. There are a couple of apps that provide fields that do, but they're specific to the apps, they're not user custom fields. Best you can do is add a custom field which is a select list and and add it as a column to the backlog. You'll see it in plain text.

Welcome to the Atlassian Community! Could you explain what you mean by "grouper UI"?

Welcome to the Atlassian Community! You cannot inject javascript into Cloud, so, the simple answer is "no".

Um, you've already got that - the view you are configuring only appears on the parent issue view, which has the key at the top of the view panel.

@Radek Dostál is right in all of this. You're going to have massive problems working with such a field. Every issue create, edit, view or transition screen with it on is going take ages to render as the server is going to have to hand over the list of every option on every load. There is no chance of the admin screen ever…

Welcome to the Atlassian Community! I am not familiar with this connection or how you might be doing it, but check the exact settings for "component" - you've capitalised it, unlike the others, and Jira doesn't always refer to the field as just "component", it often uses components or component/s (because the field can…

Apps can't help - this is a structural thing. Issues can appear on many boards at once, so there's no way to know which board rule you might want to apply.

There are three ways to work with field visibility by project (and/or issue type). @Rilwan Ahmed and @Alex Koxaras -Relational- have covered two, but you can also use a "hide" flag in the field configuration. Note that if you hide a field, or remove it from screens, then it remains on the issue - there's still a place to…

Are all possible status (in the projects the board looks at) mapped into board columns?

Could you show us a sample of your output?

The short version is "you don't". You've bought a subscription (the level of which @Alex Koxaras -Relational- has already explained). There is, of course, a version of the software behind it, but, as @Barnali Putatunda 's linked question partially explains: You can get the current version from the HTTP headers The version…

It's fine about "ticket". It is widely abused in the IT industry, and it's not helpful in Jira because it can't clearly identify whether you're talking about an issue or a request. Anyway, it looks to me like you have two incoming email functions here, whilst they won't interfere with each other or block things, they do do…

I've closed it for you.