Comments
-
I think what you're asking for requires a hack to the templates, so you can't do it on Cloud JIRA. (The "issues in epic" section is a function of JIRA Software, so you have that. Everyone with JIRA has "Core" - Software and Service Desk are applications that can be added to Core)
-
Yes, that will work fine. I'd do a little more checking thogh - don't just look at the creation date individually on an attachment - I'd look at all of them for the issue and work out the created date of the most recent one before deciding to archive all of them. That's for neatness mostly. Either an issue has attachments…
-
It's feasible, but ugly * Your script will need to read Jira to find out what it can move. It'll need to filter for "updated is over a year ago" * The attachments directory has a structure that's easy to parse once you have an issue key * Moving the attachments will break them in Jira - they will still appear there, but if…
-
Question 1: Yes, this is a good idea. Moving the attachments to another disk with more space will solve the problem. However, you suggest moving Jira_home to SAN. Do NOT do that without doing a LOT of testing. Jira_home contains other things - working files, plugins and so on. Critically, it contains your index. The index…
-
You'll need to find an SSO system to do this, or write something to make Jira aware of the OS login.
-
What do you mean by "pass through authentication"? What do you want to happen here?
-
What do you mean by "screen size"? It's filling the whole browser window for me.
-
The fact you're getting the setup location means there's somethign useful coming back from the server. That implies your network is blocking the next response, or your browser isn't getting it.
-
The flag I mentioned on your other question will solve it.
-
Ah, ok, it's using IPv6. I half-answered that on your other question (sorry - I didn't realise it was the same person!). I say half because all I've got there is a workaround - you'll be able to use CentOS 7, forced to use IPv4 (actually, just the Tomcat running Confluence will use it). But Confluence ought to work on IPv6…
-
That doesn't sound like a server error. Could you try a different browser? (Or even just chrome in private browsing mode)
-
You don't. Server.xml is only telling it what port to listen on. How other computers get to that port is up to your network. localhost is always "this computer". Your VM has another IP address it exposes to your network, so replacing localhost with that IP address means "go to that VM". You can then use DNS to give it a…
-
This is a forum for users of Atlassian software. There's nothing wrong with asking questions like this here, but as you've not mentioned Atlassian systems in any way, there's not a lot for us to actually answer you with.
-
Depends. If you have a full commercial licence for your production server, and the dev/test servers are just for supporting that production server (i.e. to try out new versions of the Atlassian apps, test plugins, try different configs etc), then just download the "developer licence" you can get from the licences page on…
-
Dropping a whole database out just for this probably can't be called "intelligent", and the closest you can get using OnDemand is to export it daily (and then you're into painful scripts which will be hard to maintain on upgrades, or recreating entire system copies to do the compare in any useful way) Assuming by…
-
You're probably missing the ones provided by other add-ons or Applications
-
No, that requires coding, which you can't upload.
-
Same place, but I'm not sure you can disable modules in Cloud.
-
Go to the UPM -> Manage add ons, and look for the system add-on that provides project blueprints/templates. Most of the project types are modules, so you can disable the individual modules and they'll vanish from the list.
-
It's one user. The important count is "a user who has the right to use the system". Doesn't matter if you get that right granted by being in 72 different groups, it's a single user using a single licence.
-
People have covered most of your question already, but I'd like to point out that your thought 2 is impossible. You can't "block" somethign in a listener because a listener happens *after* the event, so it's too late.
-
We need to see more of the error than that. Java's default error is NPE when it's not been told a specific error to throw. We need the handful of lines immediately before and after that (not the 1000s of lines it's probably thrown at first though - just start with a couple of lines before and 5 after)
-
Because it's not an internal technical detail - it's a critical piece of the configuration. That's it really, it's too important to hide.
-
You could use two different screens. Or you could define a single drop-down and give it different "contexts" for the different type. Go to custom fields, and find your field, and click configure. You should find you can add a context with a different list of options, and then say "use this for bug" and "use the other…
-
So you are using different issues types, so you do actually need it to support the capability to move issues to other projects.
-
It's an edge case - you might well be the only Jira user with only one issue type.
-
Sorry, yes, I forgot, you need it on the create screen because you have to set it. You can't work without it, you *have* to have it.The answer remains the same though - you have to have it there because it is an absolute requirement. Doesn't matter if you have only one type (that's vastly under-using JIRA's power), the…
-
You don't. Issue type is less of a "field" and more of a "critical key structural concept for a JIRA issue" and hence it is completely mandatory, even if you have only one type in the project (or indeed whole of JIRA). Although you can get rid of it on edit, create and transition screens, it's always going to appear on…
-
I think that's pretty much what my cousin said - your process has three steps, but you're trying to wedge two of them into a single step.
-
No, the assignee is a single user field, it always contains one single unique user (or unassigned if you have that enabled) I know assigning to multiple users has uses, as does assign-to-group, but Atlassian do not implement these. You can try using a multi-user-picker field instead, but it won't have the functionality of…