Comments
-
Run a search for "issuetype = epic", save it, and use it in a "filter results" gadget, making sure you include the status column. I'm guessing you probably need more than that, but you have not defined anything else, so I can't be sure.
-
Ok. Can you look back through the log from there? You should find a line in it that says "Database URL" - what does that say?
-
It's the end of your board filter. A board, and hence its reports, need a filter to define what to look at. You've told your board to ignore closed issues. So it can't report on them. You need to drop all the sprint related stuff in the filter. JIRA is already trying to handle that for you, you don't need any of it and…
-
Because you selected the old one. Could you repeat the test selecting a user that does not have two entries?
-
It sounds like you assigned it to "Nick". That's working fine as far as I can tell.
-
Try an lsof to see if you can identify what process is opening and holding open too many files on the machine. (It may be Sourcetree, I'm not trying to shift the blame!)
-
What have you done to try to fix it?
-
"It doesn't work" does not give us any information to go on. Have a look through https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-version-2-tutorial to get started on how to use REST.
-
Go check the project that the issues live in. Have a look at the project admin screen, where you'll find the "issue type screen scheme". Work your way down into that, looking for the "edit" screens for the issue types you need to change.
-
Read the marketplace entry, it says "this is not available for Cloud". It sounds like it is on the way, but it's not available for Cloud, whatever the Xray site says. (Also note the "available soon") No, it's not weird that a "component is available, but not the component's platform". A lot of add-ons are written for Jira…
-
Sub-task is not a field. Sub-tasks are issues in their own right and there's a whole panel dedicated to them on their parent issues. I'm not sure quite what you're looking for, unless you just mean "put a link to "create subtask" on the main issue display"?
-
No. The Connect framework for add-ons is not going to be implemented on server, and the ability to add server add-ons to Cloud is limited (you can only add the handful Atlassian have chosen, and they are shrinking the list, not extending it)
-
I'm afraid that doesn't change the answer. If it connects to JIRA over SOAP, then you have an old version of JIRA. That is not the problem though, if you say it's working for other people, then it's absolutely somethin on your machine, not the JIRA side.
-
Ah, Cloud. Xray has not been built for Cloud at all.
-
It's the other way around - you should be asking if Xray is built for the version of JIRA you are looking for. You should have found https://marketplace.atlassian.com/plugins/com.xpandit.plugins.xray/server/overview simply by typing Xray into the search though.
-
We can't really help you with this because: 1. JIRA no longer has a SOAP interface, it went away several versions ago. It doesn't look like it to me, but is it possible that the target JIRA has been upgraded to one that has no SOAP? 2. If you are still using a version that does have the SOAP interface, the error you're…
-
The Cloud instances I have access to are ok. It might be that yours is undergoing maintenance or upgrade, which usually lasts only a few minutes. If this persists for more than a few minutes though, then raise it with https://support.atlassian.com to find out what's wrong and get them to fix it.
-
It can be an easier option to try a clean install. Renaming the installation and data directories is the best way to do that. Stop the current installation and then * Rename your jira-home directory * Rename your jira-data directory * In most cases, /etc/init.d will contain a jira start/stop script. Rename that too. That…
-
You'll need to go through a migration - see https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html
-
No, it's not possible on Cloud, you can't inject the code. Do it properly, with separate fields.
-
Looks ok structurally, but the fact you said you had to create it implies a broken installation. Even if the install is ok, you still have the problem that the database is not set up to listen to your JIRA server given those connection details.
-
Your database is not letting JIRA in to use it. You need to give it the right credentials and database settings.
-
It sounds like you may have still had the old one running in memory while installing the new one. A reboot should have fixed that, but to find out why you can't access your new one, you'll need to debug it. What does the log say it is doing when it starts up? Errors in there? Also, define "cannot access it" - blank screen?…
-
The link is a convenience to make life easier for your users. The only way to remove it without code change is to make the user un-assignable and/or unable to assign issues, which will of course affect their ability to be assigned or assign issues globally. The share option is much the same, although there are no…
-
"Unable to connect" suggests you haven't started the service yet. Have you tried starting it? What does the log say?
-
1. Not by component, as components are a way of breaking up projects in JIRA, they're not the same thing as the Asana components. You're pretty much expected to set up separate boards for that sort of level of detail 2. There is no heirarchy like that in JIRA. Components are simply an attribute of an issue for tagging…
-
No, JIRA is an issue tracker, not a documentation system. That's why Atlassian wrote Confluence!
-
Always a good one if it's got Wittified on it. I was only talking about core product.
-
Go to the "issue type screen scheme" in the project, work out what screen scheme is in use for the testsuite issue-type and that will tell you what screens are in use. Add the field to them - most importantly, the "create" screen.
-
Yes, you need to add the field to the screen that the sub-task type uses.