Nic Brough -Adaptavist- Expert

Not that I can find.

Ah, I see, it was an external call. To add a button there, you'll need a script-fragment, provided by an app.

The technical answer is "no". Screens and workflows are configured by issue type, not users. This is a good thing - the whole point of an issue tracker is that everyone is seeing and using the same thing in the same way. While you can work together on something that looks different to each person working on it, it's a…

This is quite a hard one to explain, but there is a subtle difference between changing a field value and changing the content of a field value. Jira stores labels in a list which then becomes the value of the field. The change history records changes to the values of fields, including the to and from. For simple values,…

Yeah, it's a pain. A quick fix would be a warning on the quick-filter and swimlanes screens that says "don't bother with order here, it ain't going to do anything", a better fix would be to not validate JQL if it includes a sort. I'm not sure implementing sortable swimlanes would be a good idea without thinking through the…

This is usually down to some code that does not write the right thing into the index when a field is updated. A bug in other words. It is also possible to get this broken index if You may be able to fix it by running a re-index on the project(s) or whole system (background so people can carry on using it), but doing that…

There is no way to do this. Administration rights means you have admin, and delete project is part of that.

> "discovered that I can use the ORDER BY in the swimlane JQL query" Who told you that? Swimlanes can't do anything with order by, because the board filter determines the order on the board and swimlanes are part of the board. It's valid JQL, so the system accepts it in the JQL definition, but it doesn't do anything with…

Releases in Jira do not have a workflow, they've got a simple open/released/archived flag to give you their status. Some of us represent them as issues, and hence create an issue type of "release" which can then take on a standard Jira issue workflow (and we usually do some coding or scripting to tie them to the Jira…

Has someone added the resolution field to the "create" screen?

The picture is too small to see, but the issue key is on the right hand side of each backlog item line.

That's incorrect. If a story is too large for a sprint, you either split it into smaller stories, or promote it to an Epic and reduce it to managable stories. Scrum says nothing about the use of sub-tasks.

To import subtasks against existing parent issues, give the key of the parent as the map-able parent ID

It means someone tried to log in with a valid username, but gave the wrong password.

You've almost written that code in your question - you can translate your three "if" lines almost straight into code for java or groovy

I would very strongly recommend that you move away from the database. There's an error and an incorrect assumption in your query that means you'll be getting completely the wrong thing from it.

That's what the script I pointed to does. If it's a post-function, it'll have $issue available. The console will not, you will need a line of code to tell it what issue to work with.

Sorry for the delay, but yes, exctly that!

It's more of a networking problem usually, but you can get a lot more information about the problem with some simple server-side work. Log into the Jira server on the command line, and try "wget https://<whatever the base url of your server is>". This will either give you a connection error with a something you can look up…

Tables in Confluence are stored as part of the body of pages. You will need to find or write something that can retreive the content of a page, parse it to find and read the table, and translate it into some form 1c can understand.

Confluence is simply using a database as a data store. It doesn't need "parameters" to deal with what it's storing, and your problem is errors coming from SQL, not Confluence. Whatever issue you're having, it is with the database. I'd start by looking at the error you're getting from the workbench, what is that saying?

If you are in the context of a page when you hit "create", Confluence assumes the new page should be a child of the current one. If you do it when there is no page context, it has to assume something, and that is the "home" page for the space. You'll need to create the page and then move it up a level in the tree, so it…

Why? What problem are you trying to solve? I ask because a second key is pretty much useless to you. If you do it in text, you can't usefully report on it. It won't be a key for the issue, just a number or string that happens to be on it. You can't using for linking, inside Jira or externally. I can't think of a good…

Delete is a project permission - check the permission scheme for the project.

The server supposed to be serving up the site has stopped or moved. If this is a Cloud system (domain url ends in .atlassian.net), get in touch with Atlassian support over at https://support.atlassian.com/contact If it is a server/dc system, you will need to ask your administrators what is happening

I don't think killing Server was a bad idea in itself. But killing server when the alternatives are unsuitable certainly is. There's three alternatives: Migrate to something else (bad move for Atlassian) Migrate to DC (excellent move, but way too expensive for many) Migrate to Cloud (simply isn't ready enough for most…

Comparing story points with time spent is like comparing apples and buildings. They're totally different things and there is no useful equivalence you can draw. If you can do it in your process, then consider dumping story points and just using hours as your sprint metric.

Because the status has not changed yet. It only changes after the transition. It's not a field, it is a display of where the issue is in the workflow, and during a transition, that is "in the starting status".

If you're entering known data, automate it, there's no need to template anything. Templates for form based data just let your users ignore the questions you want answered. If you genuinely can let them ignore a question, why are you bothering to ask?

The sample code worked fine, it's straight out of the docs. The search you posted was nonsense because you put in "filtername" instead of a JQL search. That's where the function was choking on "valid operators" you had not put in a real search.