Nic Brough -Adaptavist- Expert

What is providing the New-JiraIssue command you are running here? It uses a library to access Jira somehow

There's no way to do this, fields are data on issues, and hence they're always there. What you can do is not offer the field for create/edit in general, and only ask people to fill it in during a relevant transition. My usual example of that is when you have an Incident issue type - you probably want fields for "root cause…

Not sure what Glenn Research Centre has to do with Jira (other than I know NASA uses Jira), but there are plenty of apps that offer Roadmapping in Jira. And, of course, there is Atlassian's own recommendation of their app - Advanced Roadmaps

Welcome to the Atlassian Community! My guess is that someone may have changed the project key. Your automation will have been set up to create sub-tasks in project ABC, but that's not there any more.

That would make your backlog, sprint planning, and board reporting complete nonsense, so, no, you can't do it. You can't plan or track things if you're not measuring them the same way. You can put multiple estimates on issues though, so by all means put story points on one thing and time estimates on another (or even…

Is the field deinitely defined as a numeric field?

Nope, the link you've given us is absolutely not a Confluence app. It's a file with two (non java) metadata files and a couple of binaries in it, there's none of the structure of a Confluence app in there.

That's a really bad idea. Imagine when you look at an issue and think "ok, that needs to move to status X" and then get presented with the options: * Next * Next * Next Which one do you use to move to status X ?

In this case, I think your best option would be to * Create two new projects that are set up the same as the two projects that have too many issues * Find all the issues you want to keep in each project * Use bulk-edit to move the issues you want to keep into the new projects * Delete the old overloaded projects - it's a…

If you do this, then you will need to either * Stop using Story points as the sprint estimate * Teach your people to not use any of the velocity and burndown reporting in Jira, and stop saying they're doing anything like Scrum

They're not set in the workflow, let alone the boards. The status category is entirely a property of the status, and is not designed or intended to limit what you can do in a workflow or with your board configuration.

This is what it says it is - your jiradbuser did not authenticate with the credentials you have used. I note that your command doesn't contain anything to do with the password that you should have set on the database for that user.

Please raise this at https://trello.com/contact#/

Yes, because a (company-managed) board works off a filter, not from a project.

Scriptrunner has access to the Jira API and the underlying Java libraries it relies on. I don't think there's an html parser library in Jira because it doesn't need one. So you could write some java/groovy to do it. I would question why you want to do that though. What problem are you trying to solve by parsing html?

The search for fields that have options (like components) does not have a text search of the component names. So, no, there's no way to do this, you're going to have to add each new component name to your filter when people create a new component. The request makes me think that you might be using the field incorrectly…

It's not a "limitation", it's just supporting Scrum properly. You should not be doing sprint estimates on non-sprint items such as sub-tasks.

Generally, resource files like that would be located in the "resources" directory, probably in a subdirectory for fonts. But the engine you are putting into your app to use them could probably read them from anywhere you want.

There's (potentially) two parts to that area. The first is an image - go to Admin -> System -> Look and Feel, and you'll see you can upload a new image to replace the default Jira one The second is the "title", which is just text appearing to the right of the image, and is configurable under Admin -> General settings

"I have administration access" - that gives you the right to administrate, not do or see everything. First, check that the issue is visible to you. The easiest way is to go directly to https://<yourdomain.atlassian.net/browse/ID-1 (assuming the issue key is ID-1) If you can see the issue, we'll need to start looking at why…

If you don't have permission to see something, then, well, you can't see it. You need to grant permissions for people to see things, whether via their account or by making it publicly accessible is up to you.

You'll need to find or write an app to do that report, or write a listener or scripted field to pull that information from the issue history in a way that the existing reports can use.

Welcome to the Atlassian Community! In theory, yes, you could pick up a view event with a listener. But there are none. It would vastly overload the server. Tthink of the issue navigator returning a thousand issues, or a board with three-hundred - the load of creating 1,000 events on every run of a filter, or, potentially…

It's most likely that there is a condition on the workflow that is blocking it. You'll need to ask your administrators to investigate.

I am not sure what you mean by "windows classic workflow", I can only assume it is the name of a workflow one of your administrators created and hence you'll need to talk to them about how it works.

You'll get the wrong answer from SQL. There are system fields implemented partially as custom fields, and the number won't be suitable for your audit. Please, look in the admin interface, it won't take you long to count them up in there (6 pages at 25 per page, + 4 on the last page = 154), and it has a lot more (accurate)…

That's not a "condition", that's something that would have to be done before the workflow starts.

Welcome to the Atlassian Community! Could you explain more please? What do you mean by "Table (in Jira)"? What is this "metadata" you are looking for? Project? Issue type? etc?

You can't create new custom field types with Scriptrunner, only scripted fields. Have you not tried the built-in "project picker" field?

That doesn't tell us what the library is, but the logs seem to say you got in ok, ran a search and found nothing. Your user can't see the project basically. The code is calling a "createmeta" function which essentially says "Tell me what data you need to create an issue in this project" and the response is "you can't see…