Comments
-
https://community.atlassian.com/t5/Sourcetree-questions/sourcetree-won-t-open-gcmw-zip-error/qaq-p/652774 is worth a read.
-
Business boards do not have that function. I'm afraid you can't do it.
-
A board always has a filter, to select what it includes. Start with the board filter in the board configuration, and check that does not limit the board by type. Next look at the types - if you are looking at the backlog only, then sub-task types will not appear there (as they're mostly useless in planning). Could that be…
-
There do not appear to be any "repetitions" here - each line is a separate issue?
-
This problem can be caused by crashes, although that would only affect one or two issues at a time. The cause of many thousands going wrong is almost always broken add-ons, or broken scripts in add-ons. Take a look at the workflows and listeners that might be acting on those issues - do any of them do broken things like…
-
Do NOT touch the database, that's the sort of mistake that causes these sort of problems. There really should be a "fix" option after you've run the integrity checker - the "check" button will have changed.
-
Change the Scrum board's filter so that it includes the status "ready for sprint".
-
My desk is a little different today. I have an "assistant"
-
For the user to appear in the assignee box, they must be in a role or group that grants them "can be assigned issues". You should see them in the role or group, even if you can't find them with search.
-
This warning message appears when you are trying to swap to a different type of issue that is not set up the same as the current one. It's trying to stop you losing the data you've entered on it. Either create it as a story and then use "move issue" to change the type later (this will take you through a process that makes…
-
Yes, that's another approach to excluding things that are not in the backlog, it should work as well.
-
Indirectly, by writing a short script that parsed the xml and sent it over to Jira via REST. Not quite an import (as the interface only has manual ways to do imports), but it did the trick. We eventually dumped the export to xml and just coded the REST call directly into their system.
-
Yes, you have to place an issue in a status that is in the far right-hand column for it to be "done". That's it really. If it's not in that column, the board treats it as open. You can't really filter for the backlog directly, but you can just filter for all the status that are not in "done"
-
Jira does not do that natively (with the exception of "ask if you want to close the parent when the last subtask on it is moved to "done"), so it's either a human or an automated process. Does your workflow have any post-functions that might be changing issues? Are there Listeners configured that might be doing it? Do you…
-
Not quite. You need to set up your network as Rian says, so that other machines can reach it. Then change the base url from "localhost" to "url you are running it on externally" (it's under admin -> general configuration)
-
I'd suggest using the system priority field for this, it's a clear indicator of how important something is, and you can use whatever naming scheme you want for it. A web-push as you describe here would be a disaster for users. First, you're assuming your users are sitting in Jira (they don't, they work on other things and…
-
Not exactly. You'd probably want to save some money - reduce the core licence to 1000 and buy 1000 Software (Software and Service Desk licences include Core access as discussed above)
-
As an admin, you can change the setting in General Settings for people to land on the home page of a space instead of the dashboard.
-
It's going to be ugly and probably give you false positives, but look in the table "searchrequest". The plain strings of filters are in there, so you'll need to parse them for "project =" and "project in" type things
-
Why don't you do this properly and use a labels field instead of a redundant text field?
-
Can you still reach confluence on the vm on localhost:8090 ?
-
I have just noticed that I have made a mistake. I looked at Confluence 6.2, not 6.0 (In my very weak defence, it was because a client I was not expecting to upgrade did it without warning. But that's no excuse for not checking versions) I don't think there's any point raising a bug for this against Confluence 6.0. As 6.2…
-
We can't help you based on a vague title and no information on what docs you have followed, what you did and what "unsuccessful" means.
-
This means either that you have note entered data for the estimation statistic chosen, or you have not set the board to use the right statistic. Check your boards is set to use "story points", and that the issues have values for that.
-
That doesn't sound right. Close asks me if I want to discard it or save it as a draft in a popup
-
Personally, I'd never recommend a silo'ed approach - openness and collaboration is far more productive than silos. If you do want silos though, then I can't really tell you without knowing a lot more about your organisations ways of working. Either might work for you, but I can't know.
-
Easiest way is to go to Admin -> Custom fields and simply scrape the list from there.
-
Start with a look at https://confluence.atlassian.com/adminjiraserver073/logging-and-profiling-861253813.html
-
When you install 7.8, just make sure you tell it to install in totally different directories to the old one. You will also need to run it on a different port (change server.xml in the new install) This also assumes you're working on one server - you might want to check the server is powerful enough to run both Jira systems…
-
I'd double that $0.02, it's exactly what I'd recommend too. The only thing I'd add is that the memory consumption of disabled add-ons, while minor and usually negligble, does become measurable when you're looking at complex add-ons, so if you are worried about memory, aim to remove them. I'm often of the opinion "turn off…