Comments
-
Hmm. I get an "issue moved" event when I do it. Are you using the "move" option or just editing the issue type in an edit screen?
-
Bother, I can't +1 that.
-
JIRA does not have a "notification" field off-the-shelf, so this is something one of your admins has added. You'll need to get them to check what the intention of the field is, and how they've set it up to be sent emails, as JIRA assumes basic security and by default only emails people who have permission to see the issue.
-
It will appear automatically in "business" projects, as long as the workflow supports it (typically one workflow for all issue types, with no clever looped transitions)
-
There are no permissions that are shared between global and project permissions. Unless you're looking at something new in an EAP I've not looked at?
-
Probably. A kanban board will only kick in for Software projects. Core does have "business boards", which are Kanban-very-light, so I wasn't sure if that's what you were looking for, but for proper Kanban, yes, swap to Software
-
Ah, good, that's better than I expected. What type of project is this? Business or Software?
-
What do you see? A blank screen? A blank area within it? An error?
-
There's a specific global permission for "create space". You can leave it with admins. The pages within a space though, no. It's the same as any other page. But your space admins can control which page is home.
-
You have to be a member of the level to be able to see the level in the drop-down.
-
I'm confused on what you are looking at now, and what you're trying to accomplish.
-
Because you've put different lines in the data.
-
Ah, I see, you're using the checklist add-on. The mandatory field check for this type of field simply requires that there are items in it.
-
Ah, I see, it's not changing at all, but you need it to. There's no way to do this with plain JIRA, but there are a number of add-ons that provide a post-function that can update the due-date when used.
-
Yes, you've pretty much answered your own question - you can write a filter for status = "ready to test" and issuetype = "test task" and project = xyz and sprint = XY
-
I'm afraid it does not track the transition. There is probably another way to see it though - why have you got more than one transition from the old status into the new? I assume there's a good reason for it, and that the data is probably going to reflect which transition was used.
-
Go to the Jira dashboard, and add a "filter statistic" gadget. Put your filter in it, and then select "issue type" as the statistic. It will have x and y the wrong way around, but it is the closest you'll get without coding.
-
Ah, I see, you've misread the documentation. Atlassian will not support the use of anything other than the bundled Tomcat. If you run Jira on your own Tomcat, you are unsupported. Use the installer and follow the installation guide.
-
It's limited in flexibility and imposes extra load on the Tomcat that's already loaded by running JIRA.
-
I suspect you have an add-on providing a field that does not work properly. Could you have a look for any non-standard field types in your list of custom fields?
-
Status is not a field. It's a display of where an issue is in the workflow. You should not be trying to "edit" it. If you want to change a status, you should use a workflow transition from the current status to the new one.
-
I am sorry, the question is not clear. The due-date on an issue does not change unless a user edits it. If your due-date is changing, then you must have installed something that changes it on transition. Or, you are not looking at the due date, it's something else?
-
I don't understand what you're saying here. Comments are a separate thing to fields, so I'm not sure why you mention them. Screenshots might help?
-
I'm afraid you need to push the issue through a transition that clears the resolution. When you move an issue into another project, that really is all it does. It checks the config for incompatibilities and makes the minimal changes required, then moves it, with existing data.
-
You don't move issues from one board to another, boards are not containers for issues. Your boards select issues based on their filters. The burndown chart is looking at the "done" column on your sprint board, so if you were to transition issues out of that column, then yes, your burndown will be affected. But you can…
-
1) Yes, it will continue 2) If you can't find the space, it's been deleted. The process deletes the "header" last, and the header is the bit that tells Confluence that there is a space there. I've seen this a couple of times on large space deletes, I've never worked out why the error is thrown even though the process…
-
No, but it was removed in later versions of JIRA, when the project panels were redesigned. What version are you on?
-
There's no way to do this, unless your filter/board is static. Then you can simply put a link in a text gadget There's no way to do it without another gadget - the filter gadgets list issues, and allow you to click on them to get the filter they represent, but they've no way of knowing that you might want to jump out to…
-
For new projects, the create project "wizard" will ask you for a type of project and should offer you a couple of service desk types. For existing projects, go to project admin and change their "type" to service desk
-
The multi-level-cascading-select field is not supported by Service Desk. I don't think the vendor of the add-on can actually make it come through, I have a feeling it would need coding in Service Desk to allow it to be exposed.