Comments
-
The default limit is 10Mb, so your file is way under that. I think you need to read the log file to find out what the server is doing with it.
-
There is no function for "merge", as people making service requests generally don't expect to have their requests lumped together. You'll need to find or write some code that can do whatever you want from a "merge" (I'd assume it's really "copy bits of one issue into another and then delete it)
-
The best option is probably a post-function (maybe an automation function too, although I'm not sure it can do this. Or possibly a listener). It will need to read the assignee, and if blank, set whichever user you need in there.
-
What do you mean by "manually change"? What are you trying to do and how and where?
-
In Edit-permissions mode, you can un-tick any or all of the permissions you have previously granted on any of the lines. To completely remove a line, untick the "can view" (Anzeigen) one and save the change. You don't need to do the others. Confluence has the sense to say "if they can't view the space, there's no point…
-
JIRA shouldn't even be looking for that table, it's not part of it. Are your JIRA and Confluence installations completely separate? Could they be interfering with each other?
-
So, the edit screen, as I said.
-
Boards do not have a direct relationship with projects. It's indirect, where a board has a filter that includes a project - that's the only link between them and it can change. A sprint belongs to a board. So if your board does not include a project, that project does not have anything to do with a sprint. Start with a…
-
You could write a scripted field to do it as described, but all it would do is (pseudocode) return issue.status Which can already be exported and printed, and you can get from the status of the issue. I'd want to ask your client for more detail, as the requirement seems to be "repeat stuff you already have". I suspect…
-
The problem there is that you're talking about (often rapidly changing) configuration of an application, rather than more static code. There's not even a convenient or standard way to generate "code" for this config level work. That said, I've done something like it. Generated an export and stuck that in source control…
-
In what Atlassian thing is this to be done?
-
Generally, the best option is what you've done, replacing old incompatible add-ons with their updated versions. Could you give us more detail on "custom fields not loading correct data"? What are the fields and their types?
-
No, because you're working in two separate independent systems. You'll need to find or write code to do that, and you've got two choices * Replicate a project or projects, so that project B exists in both and then use an add-on or custom scripts to make updates on both sides * Inject a new create issue screen into one…
-
There's several possibilities, including * There are no versions in the project yet * You don't have the fix version field on the edit screen * You don't have resolve issue permissions which allow you to set the version That covers most, if not all, of the reasons for the behaviour you are seeing. My guess is the first one…
-
Or even just "issuetype = Milestones". You can add the date (and other fields) to be seen on the issue navigator and you've got everything in a single filter then.
-
I think we're missing some context here. What's wrong with using the status field display? That changes when the status is changed.
-
Your customers need to have accounts in order for them to interact with the system. Even if they don't log in, you have to have the account in order to say "this person logged it" Customer accounts are free, but very limited, they don't need permissions other than "they are a customer".
-
When you restore a Cloud download, you get a default system account created so that you can go in and change other users passwords are required (remember that your download contains users, but not the Cloud infrastructure that supports them). See…
-
Yes - https://www.atlassian.com/software/jira/pricing?tab=self-hosted says for 13 users, you'll need a licence at the 25 user tier, which is $1,800 JIRA works in any environment that runs Java, but most of us would actively recommend running it on an operating system that you know best. Given a free choice without looking…
-
Unstable versions of Confluence are released as "release candidates", not full versions. Any version you find on the list of standard downloads is stable. Yes, there are often problems upgrading, mostly caused by unusual usage, volume or add-ons. I'd strongly recommend taking your 5.3 to 5.10, then 6.1 (5.3 to 6.1 is…
-
You have a very old JIRA and hence a lot of reading to do. You'll find all you need to know to answer this question from version 3 to 6 on https://confluence.atlassian.com/jira064/jira-6-0-release-notes-720413895.html Then for 7, as you mention Agile, you probably want to go with JIRA Software (it effectively replaces JIRA…
-
I don't think there's an importer for Axosoft, so you'll need to get the data out of Axosoft converted into a format that one of the "JIRA Importers" can understand. I don't know Axosoft, so I don't know what it can do in terms of export, but you may need to script or code something to do that.
-
The issue view screen is hard coded to lay out items in panels with logical grouping of the fields - you'll note it pulls out users, dates and system fields from the list, and then custom fields are left in the last section. There's no way to code the "system field" panel to have arbitrary custom fields added to it. So,…
-
Not natively, as there are so many different things people might want to do with fields on issues and their sub-tasks, there's no code for handling a wide generic case. Issues and sub-tasks are separate entities, so there's no simple rules for a relationship. You are going to need to find or write code to implement the…
-
Check the notification scheme for the project. It needs to say "Issue commented: Assignee", so that it knows to email you on comments.
-
A board is a view of a set of underlying issues, and the issues shown are the ones selected by the board filter. You have not said how you are telling JIRA how an issue is either "design" or "code", beyond telling us it is not via components. If you are doing it with, for example, a custom field, then the answer is easy -…
-
Workflows have two main components - status and transitions. If you are changing status, this can affect issues, but only if an existing issue is in a status you have removed. Issues must have a status, so it needs to be migrated to a valid one, and JIRA will ask you when it spots you doing that. Transitions are active…
-
In the sense you've just phrased it, it's not customisable at all. As a JIRA admin, you have very little more power over the setup than you had as an admin of a Cloud instance. But, on server, you do get System admin (which does not really affect the front end config hugely, as that's your JIRA admin's job, but does mean…
-
You'll need to hack core code in order to do this. That's not a great idea in itself, but alert boxes are also bad for the users. If they are trying to create an issue, let them.
-
You have told it to look at the root of the disk, then /backup/karrie.zip JIRA imports are loaded from <jira home>/import, so it needs to be relative to that. I suspect all you need to do is skip the leading / - try backup/karrie.zip. If that doesn't work, try brute force: mv karrie.zip to…