Comments
-
I'd start at https://www.atlassian.com/resources/experts (Usual disclaimer, I work for one of these people, so I'm not going to get into recommendations etc)
-
There's a lot of coding to be done here, I think you need to find a developer. Before you do, I'd also rummage through the marketplace for plugins that might help you. I've not spotted one, although I'd take a look at JETI and possibly the script-runner The bit around "write a post-function which sends email" isn't that…
-
Ok, that's a perfect response to my question :-) This is going to need some coding. My instinct would be to do it via email and put the code in a "post function" add-on which you can simply add to the "close" transition. I guess you could fire some form of "export to local machine", but you're then talking about users…
-
There's an obvious answer here - look at the issue you've just closed. The issue view contains all of that. The question here is really what do you mean by "generate report"? What are you expecting to get out of Jira? (Yes, "all the data for the issue", but where? How?)
-
No, JIRA does not do "field level security". What you see on the "create" screen is the full list of fields you put on it. If you simplify it by removing fields that you don't need, you simplify it for all users. However... There is a function for individuals to remove fields that they personally don't care about - look to…
-
See https://jira.atlassian.com/browse/JRA-4446
-
Those are system fields, and not accessed the same way as custom fields. Have a look at the "set" functions in the REST API for them.
-
This is caused my mistakes in your jira.xml or ROOT.xml. See https://confluence.atlassian.com/display/JIRA042/Installing+JIRA+on+Tomcat+6.0#InstallingJIRAonTomcat60-5ConfigureTomcatand look for the "resource name" instructions
-
Er, that's absolutely clear on where the error is - you've messed up the entityengine.xml file. Correct that and try again.
-
<edit - this was posted when there was a chunk of log in a comment> I'm afraid that does not tell us anything new. Your Jira installation cannot get a connection to your database. Either your database is not set up correctly, your network is not set up to provide or allow the connection, or you have not got the right…
-
Can't read it, it won't download, and my security software really doesn't like that site. Please use a simple pastebin or post the errors here.
-
You can post the text of an error here, it saves time (screenshots of plain text are slow, clunky and often don't help much because we only get a fraction of it) The errors you are getting are probably happening because Jira is not able to talk to your database correctly. Check the logs above the error for database related…
-
See https://confluence.atlassian.com/adminjiraserver071/managing-project-roles-802592463.html for the roles, and for adding a new user, look under user management and you'll find an "add" button
-
Hmm, good question. I can't recommend one over the other - I've only ever used the Botron one.
-
That backs up everything and restoring it into another JIRA scrubs ALL the data in the target JIRA! It's ok for creating test systems, but it's not migrating the config between instances.
-
There is no export function for configuration. Botron's Project Configurator addon is the only thing I've seen which can do export/import for your use case.
-
If, by "certify", you mean "support", the answer is "No". It is only supported on Tomcat.
-
Have a look at the space permissions - "comment" is a separate permission to "edit", so you can have a large group of people view a page, a small group edit, and another group able to comment (and the groups can, of course, overlap) However, as you fear, the view permission is not granular. You can either see a page and…
-
You still don't say if it's for affected or fix version, but the answer is the same for both - search for version X in the version field and then use one of the issue navigator display options like Excel, RSS or XML.
-
Depends on the report. What do you want from it? What does "according to each version" actually mean? Do you mean "Find all the issues for version X and report on them"? Fixed or Affects version (or a custom version field)?
-
That's a little vague, but I'm assuming you mean "stuff you've written on Confluence that is documentation". Two steps - first expose your Confluence installation to the internet, and then secondly make sure it's permissions are set to demand a login before people can view any spaces.
-
Not in the UI that I can think of directly. But the log will have "indexing" lines in it, and I think the admin audit logging will catch it as well, as long as it is enabled. I'm not entirely sure how much use it might be though - the index is also updated whenever an issue is touched, so technically, the system was…
-
No. Issue types belong to the project, they are not determined by users.
-
There's not really enough of the error message to say (the log should have more details). But I'd say you've removed a custom field plugin without deleting all the data that was on issues for it.
-
There's no "rel" stuff here, just a (correct) bar graph for velocity
-
That's exactly what I mean - you've just given us a string of numbers with no detail. We can't tell you what you're getting because the numbers have no source. Where are they coming from? What are the charts showing? What are they based on?I think this might be easiest solved if you could start by showing us a screenshot…
-
Releases and velocity are not automatically in sync, as it's possible to burn down things without release. I'm afraid you'll need to go into more detail about what has happened in your srpint and what is wrong with the reports.
-
NO. Never suggest using the DB, it's wrong and will break. REST is absolutely correct. The Blog is out of date because it shows you how to configure JIRA versions up to 6.3. From 6.4 onwards you have to use REST.
-
What is going wrong on step 4 that is stopping you?
-
It depends on what you mean by "redirect". An http redirect is easy - just whack a bit of html on your page and people will be redirected when they land on it. I suspect you don't mean that though. I think you might mean that you want that domain to be where your OnDemand installation is hosted. Atlassian don't (yet) do…