Comments
-
I didn't know about the [tags] prefix, that helps a lot, but it's not intuitive - ideally, you'd treat tags as the first thing to search as a keyword, then the [tags] thing becomes a "I only want to search tags" Here's a simple example. If you type "jira subtask" into search, you get hundreds of results, most of which…
-
Ah, it's not just me suffering more and more slowness. As for searching, well, um, one thing about Answers was "it's a nice idea to put everything in the same place and then encourage users to use labels". But the fact you can't actually search on them usefull renders it pointless. In the old forum, where search worked, we…
-
Setting up and changing mail servers is a restricted function on Cloud - you can't do it.
-
You need to read these alongside the permission scheme - what have you actually got in the default scheme? For "browse project" at least.
-
Someone has changed the users or permissions so that you can't see it. As an admin, check what the permission scheme says and then make sure your account matches one or more of the rules for "browse project" (As an admin, you can see the project header, so you can still do admin, but admin does not mean "can see…
-
Yup, Jira doesn't do field level security at all. The field-security plugin is the closest you'll get to it.
-
I've seen a few like this recently while visiting people for work, hence the reasonably swift answer! Glad you found it and it's an easy one :-)
-
Could you check the actual resolution on the new issue? I suspect your workflow has been set up to create issues with a resolution set, or the resolution has been put on the "create" screen so it's being set as the user creates it. If it actively says "unresolved" on the issue, then can you also nip into Admin -> Issues ->…
-
I'm afraid Emily already has - you have to customise the fields used by the test issue type in Jira, which means you need an administrator to make changes.
-
Yes, you can kill it off when you've used it.
-
Edit the workflow and add a transition from B to D. Then use it on the issue.
-
Add the field that you are using to indicate "important" to the navigator columns. There's no "highlight" in the sense that a line is rendered differently, but you can see and sort by "important"
-
Not a lot, unless you start trying to do "clever" things like ignore the API and talk directly to it, or run reports of it etc.Jira databases tend to be small - most users will find the database chews up a few Gb at most. On a well-tuned/monitored Jira, you'll mostly find the CPU ticks over at a couple of % usage most of…
-
Depends on your needs. Using the same box reduces network traffic and dependencies and keeps things very simple - "that box runs all of Jira". But a separate server means you know that the database server processes won't consume resources that JIRA could be using and vice-versa. So there's no simple answer to this one…
-
Check the permission scheme for the project(s) you want to stop the user from creating issues in. Remove the user from all the things (groups, roles etc) that are enabled for "create issue"
-
No, JIRA is going to pick up the "issue updated" event and fire a notification whatever you do. You do not need to hack the core code, but you do need a new listener or something like the add-on Tibor mentions. Without the addon, you will need to find/write a listener that sends an email when it detects "issue updated".…
-
It is the right way to do it - there's an incorrect assumption in your question. "for what project the sprint has been created" - sprints belong to boards, not projects, and as boards can draw in many projects, so could a sprint. Hence you have to jump through the 1-sprint:many-project relationship hoops
-
The status is a red-herring, there's no direct technical relationship between status and resolution (we tend to manufacture one in config, and that's a good thing, but JIRA mostly won't do it for you) Have a look at the two issues - what is their "resolution" field set to?
-
Simple answer is that you can't do it. The workflow an issue goes through is determined entirely and only by the issue type of the issue in the project. The other fields are utterly irrelevant. If you want to change workflow, you have to change the issue type. End of story. You *could* try to wedge this in - find/write a…
-
Yes, your normal users don't get to play with columns, so they're unaffected
-
You can either use a set scheme with all the flexibility of multiple workflows and varying conditions/post functions/validators, OR you can use the simplified workflow. It's one or the other.As soon as you set up your extra workflow and apply it to the project, it's no longer simplified, and your project admins will not be…
-
Oh, the (?) next to "this board is unable to use an agile simplified workflow" is really helpful!
-
Yes. To simplify the workflow, you have to have the project in a reasonably simple state to begin with. And, of course, after you simplify it, there can only be one workflow - that's the point of the simplification!
-
Ah, well, that answers is - you haven't got the simplified workflow, so all you can do is maintain columns.You can simplify the workflow, but you're going to need to work out why the board cannot be simplified and fix that first. The usual culprit is "I have more than one workflow in one of the projects on the board",
-
That's a little odd. Could you check if you have "add status" button next to the "add column"? If you do, can you try that and see if you can manually create the new status and drag it into the new column?
-
Nicely found - the PSD Preview plugin is the problem for most cases.
-
Ok, svp - you might want to check that the version of the drag-and-drop add-on is correct - update it if you have the option. For the rest, it seems there's a bug in JIRA Software 7.2.3, or its interaction with an add-on - I'd encourage you all to raise it directly with https://support.atlassian.com (and svp if the drag…
-
Ok, the only way I can think you can get that error is if you've got an invalid version of the Agile add-on installed - incompatible with your version of JIRA. What versions are you using here? JIRA and Agile, or JIRA Software?
-
Ok, there's something wrong with the issue view module in JIRA Software. It might be an add-on breaking it, but the error does suggest it's inside Software. Could you check the logs - ideally, have the application log open and tailing, so you can see it real-time, then click to provoke the error and see what goes into the…
-
Interesting, that suggests a very broken add-on, but possibly a system one. Do you know which area of JIRA this is happening in and what you were expecting to be there instead of the error?