Comments
-
A filter is not a project object, so there's no real way to do this. Think of filters like "assigned to me" or "company = acme" - there's nothing project related in there.
-
Give people a chance - we're a community of end-users scattered across the world, not an instant-support system!
-
A three part answer... First, don't do this, it's almost certainly a bad idea. Re-mapping status names is a recipe for disaster because you end up with two groups of people using different words for the same thing. Stick with one name for one item. Second, in that vein, think about your requirement more carefully. You can…
-
I'd place it just before "index this issue", but I don't think it really matters too much.
-
Go to edit the workflow, and look for post-functions, it should be available as one of the post-function types you can run.
-
I did it by adding several post-functions, one for each task.
-
I'd say that there's two possibilities - first, what you're providing does not match what the bank expects, or second (and much more likely), that your input is being damaged or lost on the way to the bank for verification.In both cases, it's definitely something support need to look into, as the errors we get as end users…
-
"Try again" doesn't really tell us much about the real error you're getting. But assuming it means "server can't reach the credit card company", your best bet is probably to raise a support request at https://support.atlassian.com - they should be able to get to the errors being thrown.
-
No way of knowing. I know you've said you've read the log file, and said "it doesn't show anything useful", but we don't know that. Are there any errors at all? It's very likely to already contain the message you're seeing under the description too - look in that area.
-
Ok, being able to edit/delete projects, but not see them in the projects drop-down is a classic symptom of an an admin who hasn't got browse in the project.Adding yourself explicitly to the permission scheme is a good test (I assume as an admin, you checked that the project is definitely using the default permission…
-
Check the default permission scheme - it sounds like it doesn't include your account in "browse issues" permission for some reason.
-
No. The key is for the project, not the issue types. You'd need to put stories and defects in their own projects to do this.
-
That looks like the server is too busy in general, or is unable to render the page because it's taking too long. If it is only the status list page, then I'm a bit stuck. I can imagine a couple of ways to break it (having vast numbers of status, or including jsp or html in it, or in the announcement banner, that throws it…
-
That's the server not responding to the request at all. It's possible that your Jira is running too slowly to cope - is the rest of it running ok? Also, going back to firefox, could you try it in "safe mode"?
-
Are you going there via the administration menus or from a bookmark/url? Could you make sure you follow the link from the menu? Could you try a differen tbrowser?
-
I'm afraid you're stuck. You can't do it, and Atlassian are not planning to enable it any time soon.
-
Bother. Last time I looked, https://jira.atlassian.com/browse/GHS-3573was open, but now it's been closed as "not going to be able to do it in the next year". Grr.
-
No, you're not missing anything, it's a known flaw that you can't use the boards to drag from one status to another if they're in the same column on the board. It still works in Jira (the transitions are still there), but the only option in Agile at the moment is to move it to another column and then back again. There's an…
-
Screens can be used in four places. Issue View - when you look at an issue Issue Edit - when you edit the issue Issue Create - when you create one Transitions - when you move issues from status to status There is no such thing as "link a screen to a status" - it's complete nonsense in JIRA terms (and mostly useless in the…
-
Jira numbers issues sequentially within a project, so this is correct behaviour. Jira doesn't let you change the key of an issue, unless you move it into another project. (The whole point is that the keys are unique) So, the short answer is that you can't. Deleting and moving issues leaves "holes" in your sequences. This…
-
I'd agree with Roman here. For large installations, you definitely want a copy of the home directory and a copy of the database after shutting the system down. Export/import is for small systems, or for changing the database if you must.
-
"advice" is pretty open-ended. All I can really advise is that you build the new server, install Confluence on it empty, do some testing, then plan and test a migration on to it using a copy or export of your current system (as suggested in the documentation), and then plan to do it for production when the testing all…
-
Attaching an empty file is utterly pointless. So I'd say this is a "pass" of a test, because it works by preventing a user from doing something utterly pointless. I suspect your "negative tests" are incomplete or poorly designed or specified. As this is clearly a correct response, I'm not sure why you are asking it as a…
-
Attaching an empty file is utterly pointless. Your browser is unlikely to send it properly, and JIRA has no reason to accept it (although older versions did give you a simple "file is empty, so don't bother" message)
-
Terribly sorry, I should have said that. "Browse project" is "browse issue", it really means "permission to look at issues inside this project"
-
Depends on what you mean here, as I can read this in two ways. If you mean "developer can only see issues if they are assigned *to them*", then you can simply use "current assignee" in the permission scheme on the "browse issue" permission, while removing all the other things that let them see it. If you mean "developer…
-
Depends on what you mean here, as I can read this in two ways. If you mean "developer can only see issues if they are assigned *to them*", then you can simply use "current assignee" in the permission scheme on the "browse issue" permission, while removing all the other things that let them see it. If you mean "developer…
-
No. You have to go through transitions to change the status of an issue.
-
Nothing in the audit log means the details are going to be in the application log. If you are on Cloud, you'll need to raise that with Atlassian support so they can investigate and fix it.
-
Change the permission scheme for the project so that it allows "edit worklog" for a chosen group (Project administrators for example. I prefer the "user can edit own worklog" option myself, it means a user can correct their own mistakes without being able to edit other people's time)…