Comments
-
When you say "administrator access page", do you mean the "websudo" popup that asks an administrator to confirm their password? See https://confluence.atlassian.com/adminjiraserver071/configuring-secure-administrator-sessions-802593160.html#ConfiguringSecureAdministratorSessions-DisablingSecureAdministratorSessions for how…
-
There is no "description tab", I think you mean you have a panel for the description. You can't add to that, it's there for the description. Custom fields will land in the custom field panel, unless they're date or user fields.
-
Simple answer is "yes" because a board (scrum or kanban) can be set up to draw in issues from many projects and work together with evertyhing it includes. Scrum boards have a lot of functions around planning of course, with backlogs and scrums.
-
I've never seen rewriting done in Tomcat, everyone who needs rewriting usually has more complex requirements than a single rewrite rule, and uses Apache to do it.
-
I think it's more a case of "we released new software. Add-ons need to be updated by the authors to deal with the changes (probably including us)"
-
CVS to SVN migration is something a lot of people have done. Subversion was written because of inadequacies in CVS, so it's a pretty standard process.I've already explained why you might want Bamboo and Subversion integrated.
-
You don't need to integrate it, but you probably want to. Start with the absolute basics Bamboo is a build server at its heart. It exists to build software from code (although a lot of us do a lot more than just build the software), automatically, so that your developers are not spending ages doing their own builds in…
-
That's good, but the log is telling you what's wrong now - it's out of memory for "PermGen" Have a look at https://confluence.atlassian.com/display/JIRAKB/JIRA+Crashes+Due+to+java.lang.OutOfMemoryError+PermGen+Space+Error
-
Your first point 2 is the correct format - jira.home = D:\\JIRA\\HOME (double slashes, no quotes) I would check that your server actually has that directory (case sensitive as well) and that the user that Jira is running as has permissions to at the very least read and write that directory and everything below it. If all…
-
The standard docs are at https://docs.atlassian.com/jira/REST/latest/But I find https://developer.atlassian.com/display/JIRADEV/JIRA+REST+API+Tutorials is generally more useful as a starting point.I think your minimum requirement is probably met with "A Jira custom field that refers back to the Remedy ID" (although I'd…
-
Mmm, well, you won't be able to keep IDs the same, unless you can coax Remedy into using Jira's issue ID scheme. Of course, the easy solution there is a field in Jira to keep the Remedy ID and a field in Remedy to hold the Jira one.You'll need to rig up something to duplicate the bits of data from each system in the other.…
-
That depends on what you mean by "integrate"? What are you trying to achieve with this integration?
-
Log in with an account that has administration rights.
-
Ok, that looks llike it's a bug in the scripting plugin, or the interface between the plugin and Jira's validator structures then. It's reporting your error message inside the plugin, but that's not flowing back to the validators for presentation to the user. I'm afraid your options are limited here - first, check that the…
-
Ah, good, that's stopped me wandering off in the wrong direction. I think that should all work, from my distant memory of the script runner in 3.12. However, as you aren't getting the script runner error, I'm tempted to suggest that it's not actually that particular script causing the problem, but something else. When you…
-
I'm afraid that doesn't make much sense. First of all, post-functions are not there to do validation on data. That should be done in validators. Secondly, Jira doesn't have any mandatory field validation off-the-shelf... So, if you're doing it in a post-function, that would explain why it's not really working - it's bad…
-
Difficult to tell from that. Either the version of the plugin is wrong, or it's configured to validate something it can't, or it's a bug. Maybe share what you've set up on this validator as well?
-
It depends on the validation you need. Behaviours and the Scripting plugin are very useful and do work well on Jira 3.13 (there's no information here to help us debug your issue creation - have a look at the log file). You could also try other plugins from the marketplace that provide validators, or even write your own…
-
Nope, you can't do it in OnDemand. The only thing you could try is importing/creating 999 duff items, then deleting them.
-
But what do you mean by "weblinks"? I can't think about possible workarounds unless I know what you are talking about.
-
Depends on what you mean by "weblinks". If you include urls in your CSV (obviously being imported into text fields, or even url fields), then you'll get urls in your text. If you mean something else by weblinks, you'll need to explain further.
-
I have nothing to add to Udo's answer - you did not map the priorities on import, and to fix it, you need to bulk edit and then delete the extra priorities.
-
Issues and users are separate things. Deleting the issues should mean you can safely delete all the new users, but there's no way to delete a user just because you've deleted an issue. They're independent objects.
-
Not really - Jira doesn't do much in the way of "reversion". You can delete the new users, but the reason it created them is likely to be because you used them as the reporter or assignee, and Jira won't let you delete them until you've reassigned them and/or changed the reporter. It's also a bit of a manual process,…
-
There's plenty of ways of getting the data out of Jira. The best way to approach this is probably to look at what Remedy can import and how you'd like to do that? Could you script it to scrape data from Jira directly via REST? XML? Load from some form of extract? etc.
-
Oops. I forgot: https://marketplace.atlassian.com/plugins/com.comalatech.jira.canvas
-
You can't. You can get to a "swimlane = sprint", but the columns on an Agile board are always based on issue Status. To create the sort of board you're suggesting here (which wouldn't be a "Board" in the Agile sense because those boards really are designed around column ~= status), you'll need an addon or report to do it.…
-
Yes.
-
Right, you'll need something that can extract that. It's a JQL function or a scripted field to pull that out so you can search on it.
-
JQL is for finding issues, not working with the results. All you really get from a JQL search is a list of issues. You then push that through some reporting (the issue navigator, reports, gadgets etc), and the reporting is what determines the output. So, you'd need to do that in the report, not JQL. So the next question is…