Comments
-
No, you need to do the migration, however you do the actual change of scheme.
-
Atlassian are revising the documentation and the restructuring has dropped that page. Older versions are available, but the "page has gone" page they've got doesn't link to the one I think you probably want - https://confluence.atlassian.com/jiraportfolioserver/installation-715262590.html
-
You can't do this. If you want rid of an issue type, then you have to remove it from the issue type scheme, either by deleting it, or by moving the project to a scheme without it. However you remove the issue type, JIRA will force you to move all issues using that type to another one. It can't function in a project having…
-
All you need is the greenhopper jar file. The easiest way to get it is over the internet, but if you don't have access on a machine, then you'll need to download it on another machine and transfer it over. I tend to use scp, but you can do it with any transfer method - ftp, file shares, even email. Physically, download a…
-
I'm afraid a lot of the rest of us have totally different experiences, so it begs the question of what you are doing differently. It sounds like you have a poor network connection and have got used to weak software tools.
-
You'll need to do some coding in both Jira and Confluence to achieve that, including hacking the status macro to support it
-
We're not support, we're end-users like yourself. You'll need to raise this at https://support.atlassian.com
-
Duplicate of https://answers.atlassian.com/questions/8618686
-
The "dried answers" you are getting from Atlassian are because this problem is not an Atlassian problem JIRA is running on your machine. You need to set up your network to allow external access. I very much doubt Jo's network set up is identical to yours. You say you can see JIRA on http://external_ip:8080 which is fine,…
-
Not a lot. Jira is running ok on your network, so it's running. The issue is in the routing - you just need to get "external" access routed through to Jira (allowing http or https access). That applies on any network.Mostly, people in your situation will have a gateway - something that external websites run. If you can run…
-
That's a networking question, rather than JIRA. To connect to JIRA on a server, you just need a network route to it. As you say it's internal (local or via VPN), then your network is currently set to allow people internally to it. You need to talk to your network team to get them to configure the network to allow people…
-
Ah, for most custom field types, you have the right idea. However, a label is a global field - one of the points of the label is to allow cross-project labelling. Your contexts control where it appears, but every label in use in the field is global. If you want different label sets, you need to use different label type…
-
JIRA doesn't really have much at the project level - projects are for gathering together issues, and you're expected to work on issues. Most of us have Confluence spaces for projects alongside JIRA, that's ideal for documenting project stuff
-
The bit in the middle of my answer - you can still *use* the Core software with an expired licence. But you are not supported and you can't upgrade to versions released after expiry.What you need to pay depends on what licence you have and when it expires. If it has not expired, the upgrades are available. If it has…
-
You don't pay for upgrades. The licence you have is for any version released up until the expiry date. Let's say you currently have 6.3 of JIRA and your licence expires tomorrow (22/11/2015). Let's also say Atlassian is going to release 7.1 on Christmas day. Even though your licence expires tomorrow, you could upgrade to…
-
Ah, we're not Atlassian support, we're a community of end users like yourself. You'll need to contact Atlassian to deal with this. I'd tend to start with sales-at-atlassian-dot-com, and include your company name and "Support Entitlement Number" if you have it to hand.
-
You probably need to tell us a bit more.
-
Most monitoring systems can monitor a url, I don't think there's any reason to choose any of them just because you want to use them with Jira. Throw a rock at google for "monitoring url availability" or something like that :-) Some of them may need you to give them an account for any detailed monitoring, or you might want…
-
You need to talk to the administrators of your OnDemand account - this would be the mojang administrators and not us We're a community of end-users of Atlassian products. Mojang uses one of these products, but we are not the admins for it. You need to talk to Mojang.
-
Component is a system field, and the list of them is project specific. You need to make sure component is valid in the target project (check the field configuration, and then if it's on at least the "view" screen - these won't stop it moving if they are not set, but they will hide it from you). Then, you need to make sure…
-
Not natively. There are some scripts and add-ons that do it, but be warned that a lot of humans don't like having things inflicted on them and they may not appreciate you doing that.
-
You've got the problem of "how do I know what to put in" no matter what you do. The issue collectors simplify it a bit because they're associated with specific projects, but there's no getting around that, it's all about the user knowing the context or having it spoon fed to them The simple approach is to use screen…
-
The "issue type screen scheme" determines what set of screens each issue type uses. You can easily set it up to say "when creating a bug in project 1, use list of fields 1, but when creating a bug in project 2, use list 2, and when creating a feature in either project, use list 3" It looks a bit complex when you first…
-
Very heavy emphasis on the "not for production use" - I've moved HSQL test databases around using that method, and sometimes it works, and other times, you lose everything. Definitely not for production (there's other things that go "bang" if you use hsql as well...)
-
I have no idea. You haven't told us what database server you are using.
-
No, you haven't understood what I said. You need to reconfigure the database to read its data from the new location. The dbconfig file tells Jira what database to connect to.
-
Stop Jira, stop the database server, move the data, reconfigure your database server to use the new location, restart the database server, restart Jira. Jira doesn't actually care where the database is physically located, it talks to the database server, not the file system.
-
It doesn't actually log these itself - the log zezeto mentions is an access log for http hits, but it might not capture everthing you'd expect.
-
The other option is the "Field Security" addon from quisapps.The bit I'd like to point out is that "Jira does not do field level security natively - you need coding or an addon to provide it"
-
I pointed to that as an example of configuring the datasource.Normal JIRA fields are irrelevant here though, they won't use or care about your new datasources. I'm not sure what you're even aiming to do with them. You said you're displaying information from the external database - that's fine, but I assume it's a display…