Comments
-
To "close" a question (not "ticket", this is not a transport, work-order or delivery system, it's a community of users discussing their problems), please use the "accept answer" button above the answer(s) that worked for you.
-
Probably most of us. Confluence went through a phase of allowing us to put the attachments in the database, but the return on investment on that was very low, causing just as many problems as it solved, and then rapidly became redundant and then incompatible with newer technologies. So, I would guess that 99.9% of…
-
No. It's hard-coded throughout. In fact, just being able to turn it off would make things worse, as we'd all end up asking every user about that flag as well as all the current stuff we have to. "Resolution" really should be thrown away as the "done" flag. If I had any control over Atlassian's development of Jira, I would…
-
Boards are designed and built to represent your issues moving through their process from one side to the other. So the columns represent status, and nothing else. To base boards on non-process related things, you will need something to draw them up differently. I'd look at the "Canvas" add-on, which lets you pick any…
-
1. Try the handler that strips previous data 2. Use an email handler that can parse emails for it. The built-in handlers are good enough for 95% of cases, where people only really care about the core content, but when you need something more powerful, you need code that can be told to understand what you guess your users…
-
It's quite well-hidden by poor web-design. Go to the Jira download page, find "all server versions", then "view all versions", then mess with the drop-downs, it's in there somewhere. (What's really bad is that while this is an utterly dreadful design, it somehow manages to get even worse if you need a version below 7.0.…
-
You'll need to visit id.atlassian.com, try to log in and then follow the recovery instructions.
-
What do you mean by "get", and what do you want from it?
-
The full xml import will destroy everything you have in the target Jira. I wouldn't ever try that on anything other than an empty Jira. To do that, I'd start again - grab the installer for the version you want, run it, and let it install. Tell it to use new directories and an empty database you've set up for it. After…
-
You can upgrade directly from any version of Jira 7.x to any higher version, there is no need to go through any intermediate versions. Most Jira releases contain all the features included in previous releases. Although sometimes Atlassian does remove features. You'll need to check the release notes to see if they have.…
-
Why are you trying to "access" the table?
-
Your App will need to have a framework that can capture data telling it which projects to show or hide it from, then use that to determine when to render itself. I know that is very vague, I am sorry, I don't do a lot of work with connect apps.
-
>Most of the 'old timers' use project roles. Heh. Every training course about Jira that's any good and deals with access has the tutor jumping around yelling "use roles". Everywhere. Seriously, get to know roles, and use them.
-
Behaviours became part of Scriptrunner several years ago.
-
That sort of makes sense, but it's a rotten thing to do to your users. Why not just ask them for the information you need in the form on the actual request? I know I despise systems that say "hey, here's some stuff, but now you have to go open up something else, save it and then attach it to the place you've just landed in…
-
There's not much we can point you at, it sounds like you are looking at the right docs to do a restore, but you're actually blocked before you get there. Is this Jira install you're working with a completely clean empty Jira?
-
Next-gen doesn't support voting yet.
-
No, seriously, you don't want to do this, it's a nightmare to write, implement or support and wrecks your chances of upgrade. The developer docs do have stuff on writing them, but it's not explicitly "type 1", it's just quietly pointed out that installation and usage is manual and risky when you get to it.
-
I think you've got it. I'm still waiting for someone here to define what the "current project" is when the board, dashboard, filter or report is set to look at "project in (x, y, z)". Until that's answered, we can't get far with this.
-
You must have Core. Software is something that runs on top of Core, it can't run without it.
-
And what version of Jira?
-
What field is customfield_15400?
-
Yes. I usually think of the server as "Software is an application that runs on top of Core", and the licences as "A Software user (and JSD Agent) gets a Core licence as part of their main licence"
-
You need to do what it suggests - ensure that custom field is on the "create" screen for the issue type for that project. Try logging in as normal and creating a Bug in project Glob - do you see the custom field? I suspect you will not, because it needs to be added.
-
By "import", do you mean "attach to page" or "read a doc and convert to Confluence page"?
-
How are you serving up your directories as URI/URLs?
-
There's no way to do it with the Message fields. A message field reads its default value and puts that on-screen when the field is present. There is only one default value for any field. So you can't change values in there. Your html would have to be dynamic, including scripting to fetch (at least) the status and use it to…
-
No. The only way to do this is to have code in the App that can ask the admins what projects it should show itself for, and then hide itself when it is not wanted. In other words, it's up to the Connect App to do that.
-
No. Very short answer, but on the surface, it is illegal to run more than one instance on one licence (it breaches your contract with Atlassian) * If you have multiple Production systems, you need a licence for each one. * If you are clustering many servers, but they all run the same Jira, then you need a single Data…
-
Ahh, Legal, yes. I understand. I have to resort to balancing "software is mostly designed to work properly, vs according to legal demands", but obviously, a lot less bluntly than that! My instinct is to get them to draw up a contract that boils down to "admins do not touch our projects until they have our permission in…