Comments
-
Yes, and that's easier, because it doesn't really care where they are. As long as you preserve the structure and file ownership/rights, you should be able to simply move the whole lot. (Ooops, I forgot, "and don't put the application in the home directory")
-
I wouldn't do this. You should have separate directories for confluence and jira, otherwise you could end up with clashing names. By all means do something like .../atlassian/confluence and .../atlassian/jira, but do not just do .../confluence (and point both Jira and Confluence to use that as their home) Once you've…
-
Without knowing where you've seen it, there's no way of knowing. Context please?
-
The first one is exactly what it says on the tin - you've managed to configure two custom fields with the same name. Rename one of them, it will be fine. The second is a lot harder to track down, as it could be anything. I'd lean towards your database connection being badly configured, your system is coming under a very…
-
Drop down fields have lists of options behind them To add a new value, you need to amend the list of options for it For Custom fields, Pedro has answered the question. There are some system fields though, which are different. Components and Versions are handled by the project administrators. Priority and Resolution are…
-
You can also use https://confluence.atlassian.com/display/JIRA/Jelly+Escalation as a model for "nudging" an assignee (It's for escalation, but it's not hard to adapt to make it comment instead of changing status. One of my colleagues set up a test with this last week and I've got an issue open with 12 comments all saying…
-
Ok, you've got two issues here. (Sending an email on a transition is a standard notification function, so that's a doddle and I won't ramble about it) First, you can't associate groups with components. They have a component lead, and that's about it. You could get a bit clever with this though:…
-
Replace the SOAP calls with a REST equivalent - look under issues in https://developer.atlassian.com/jiradev/latest-updates/soap-and-xml-rpc-api-deprecation-notice/jira-soap-to-rest-migration-guide#JIRASOAPtoRESTMigrationGuide-Issues
-
I'm not aware of a flag or setting that would remove the delete ability completely like that (hence a comment rather than an "answer"), so if it really is happening, and it's not just that the project permissions are not set correctly, I suspect you're going to find it's some form of code hack. But, when you do work out…
-
I think you need to define "integrate" more carefully - what do you mean by that? Or describe the end goal - what does the user see? What do they do, where and what effect on both systems does it have?
-
It looks like you have a version called "irrelevant", but I don't know where the link has gone.
-
Search for the issues you want to assign to the person, then look to the top right of the issue navigator - on the menu there, there should be a "bulk edit" option (if not, then check Admin -> Global permissions - you have to be in a group nominated in there to be able to use bulk edit). You can then perform a single edit…
-
Unlikely - Atlassian have pretty much said that Connect is the future and they won't be adding more type-2 addons to Cloud
-
Not on Cloud I'm afraid. The trick is to create a new project template that does what you want, but you can't install that type of addon in Cloud. Or use the project configurator addon, or the script runner (again, not available for Crowd)
-
Ok, I'm not familiar enough with those to know what the "view" is, or what the test runs actually do in Testy. I'd suggest asking these questions again, but with the Structures and Testy tags on them, so they get a good audience.
-
Ok, you have test cases as issues, that's fine. But this does not explain what you are doing: "View is also manually created. Question is if you can see on what views the test cases has been run. " What is a view? How are you tying a test case to a view? How are you recording how test cases have been run?
-
I'm afraid that does not help. You have not explained how you have implemented the test cases, what the views are or what the queries are.
-
We need to know how you have implemented these "test cases". There are add-ons that provide test case management, there are add-ons that would enable you to do things to JIRA issues that make them work differently to standard issues. You can make JIRA issues follow a particular setup that works for tests in the way your…
-
Importing or manually adding them is fine, but how are they implemented? Issues, sub-tasks, a testing add-on?
-
How have you implemented "test cases"?
-
In theory, yes. As long as you can run a compatible JVM on your AIX system, then you can run most Atlassian applications on it. It is not supported though. If you have issues with it, Atlassian could tell you to move to Linux before they'll help. (From experience, they will try to help you even though they don't support it)
-
Take a full XML export from the "backup and import" admin. There are other methods of exporting data from Jira, but that's the only one that will really get everything, the others are limited. You might get a more useful response if you explained why you want to do this though?
-
I gave you two to look at. And older versions of JMH is open source.
-
The only two that I know of are below. Both BSD licences. Neither are documented as valid for Jira 6. But you should find that the first one works for version 5, and from my limited tinkering with email handlers, I suspect it would be quite easy to recompile for v6.…
-
You have disabled or deleted a plugin that is providing one or more fields on that issue. To fix it, put the plugin back. Or, put the plugin back, delete the field from the custom field list and then remove the plugin again. Specifically your log tells you it is -…
-
Yup, I can't think of many good reasons to get that, other than to use it in code. Which isn't of much use because you can't upload code into OnDemand. Or for scrapes/REST/XML etc, which contain it already, so you don't need to ask anyone for it.
-
Dedicated infrastructure - not really, it sits on servers that are in a pool. You will not get SQL access to it.
-
What does the script do?
-
Your Kanban board has a filter, like "project = x and fixversion is empty". You can modify that, change it to some other criteria to drop things off the board. Like "project = x and (fixversion is empty or status = closed)". That one will look a bit odd - when you drag to closed, the issue will vanish without feedback. You…
-
That could be quite messy, but yes you can. It's nothing to do with projects, of course - boards are a view of issues, the project is not relevant. Create a new filter for "all the issues that would be included on all my boards" (likely to be something like "project in (abc, def, ghi)"), then create a new Kanban from that…