Nic Brough -Adaptavist- Expert

It won't - you can only use fields that have fixed lists of options to select from.

Welcome to the Atlassian Community! From memory, doesn't that app add macros/functions to Confluence? It's not something you "open the app for use", you put its functions on a page.

Your JQL could be including a huge range of issues, with lots of different workflows, so Jira is offering you everything that might get included. The last clause is probably the main one - a story in an Epic in the ACME project could be in any project you have.

There is no export of users. You maintain the list in the site admin users screens.

Welcome to the Atlassian Community! You will need to upgrade to 6.4, then 7.0, then (ideally) 7.13, then 8.22, if you want to get on to the easiest version to migrate to the Cloud. You will need to renew a licence to upgrade to any server version released after the end of your current licence.

Yes, you can add functions to inactive workflows. They won't actually do anything until you associate them with a project via the workflow scheme.

We can't tell you anything. You have not given us the error or what you're sending.

This will loop you back to the Community if you have a free, starter or community licence for Bitbucket. Is that the case for you? 

I lived with a black cat for 19 years (and her black sister for 15, and my black step-cat for 2). I don't think I could ever wear anything other than black (with a hint of cat-spit)

If you have migrated the issues, but not the table-grid data, you are going to have to go through a manual mapping exercise - extract the data from the old data, work out what issue key it is in the new one, and then import (I've not tried to export/import table-grid data recently, I don't know how to import - if you can…

How are you seeing these "credits"? Are they getting email or slack messages? What do you see in the issue history?

This can happen in some browsers when you have added a lot of apps that go into the main menu bar and your screen is not wide enough. Create and search can be navigated to in other ways, but there is one trick that may help - try making the zoom lower (ctrl - in a lot of browsers), this can separate the word and…

Not quite, but yes in this case. Your Software people have access to JWM projects - their licences let them into projects of both types. Equally, JWM only users can use the projects underlying Jira Software, but they won't be able to use the boards the Software users can. Your main problem might be that the functions of a…

I do not think you have an unsolvable problem, I think your query might be being too picky and/or looking at the wrong field, and hence excluding too much. (I've dropped the "order by" here, I think the problem is selection, not sort) project in (INFRA, "INT") AND issuetype in (Bug, Epic, Story, Task) AND status in ("CLAIM…

Not quite. The logic Jira is using here is that a text field could be anything and it is very rare that a team of humans will get text entry identical every time (heck, it's around 90% that three of us will get it wrong iin a surprisingly short time, and guaranteed, and faster, if there's more than three) So, a text field…

The first option on the list of resolutions is "none". If you select that and save it, Jira will then display "clear the value of resolution" in the summary of the post-functions.

You don't want to do that. But you are missing the point that the status and status category are not directly relevant to your sprint - you need to be looking at the last column on the board. That's the only thing that matters to "done" on an Agile board.

The only other things that might set a resolution are * email or other integrations (that would not be tied to doing things in your scrum process, they would appear to happen spontaneously, not when a card is moved to another sprint or story points edited. * Your people going into the issue and changing the resolution.…

Why don't you use the resolved field for your external reporting? It's just as readable as a custom field.

TLDR: History Jira 1 had a need to capture environment details, but no way to do it usefully with a custom field, so Scott and Mike put in a free-text field to prompt people to tell them about the environment the issue had been found in. You're absolutely right in that it's more intuitive to have a drop-down. The first two…

If you remove it, your Confluence will stop working properly. You should look at the vulnerability, check if you are actually affected by it, look at the amelioration options, and probably go with the most simple ones of firewalling, trusting your admins, or upgrading Confluence.

Welcome to the Atlassian Community! You'll get that when you do what it suggests in the message - try to read a project that doesn't exist or you don't have access to. To avoid it, you'll need to get the correct url for a project that does exist, or talk to your admins about getting access to the project.

What data do you think you are losing?

OK, so you'll need to write some code to run when a pipleline fails - it should simply send a REST call over to Jira to create a new issue.

It's the same answer. Stop botching this with Javascript and do it properly, with a post-function, listener or automation. It's what they are for.

Your code is structured incorrectly, but you have not shown us all of the code, so we can't see where the problem might be.

So Intune is not working, you'll need to talk to the vendor of Intune.

Ok, so I would recommend removing your code, as it's not doing much of any use, and can't then put scripts into the workflow transitions.

This sounds like you have a post-function, listener, or automation picking up that you have transitioned an issue and setting the resolution. You'll need to identify that and remove it.

Ok. What do you want us to talk about here? A statement that something seems to happen is not a starting point for a conversation about getting any help with a problem.