Comments
-
JIRA is issue-focussed and doesn't really see a project as anything more than a container for issues. It's not a document repository, it's for tracking issues. Most people simply use Confluence for project related documentation. If you don't have a shared documentation system, then another way to do soemthing like this is…
-
You don't need it to be identical, but you do need to have matching configuration in place. If you're importing (say) Epics, Bugs and Tasks, then your shceme in the target must include Epics, Bugs and Tasks. (It could contain other types too, but they are not important)
-
This sounds like the system is having problems writing to the index files. I would want to read the logs for the system around the time it is trying to index and see what errors are physically happening. However, whatever they say, you will probably end up with the same fix list: * Check that the permissions on the index…
-
This all depends on what you are getting from "google cloud". Can you log into the server(s) the systems are targetted at and run an installation of them?
-
Standard advice - never update an Atlassian application's database directly. It will almost always go wrong. In this case, it's a moderately simple update, and, although it will work if you follow the usual SQL path (Stop JIRA, back it up, run the SQL, start JIRA and re-index if you've touched index-related data), you are…
-
Step 6 is any time between minutes and hours. You'll have to test it to find out, because the import time is a function that is broadly "complexity x volume", and we don't have any measure of either for your system.
-
Ok, that could well be the problem. I would expect a 403 if a network setting is preventing access (including a misconfigured load balancer). That explains the original question too. I'm afraid the best we can do for an answer is tell you that it probably is the load balancer that is misconfigured, but not a lot more. A…
-
I think the advice to contact your JIRA Admin applies here. I want to read the log files, and it's your admins who can do that.
-
Creating a JIRA server is nothing to do with load balancing directly, so it sounds like we are missing some information on what you are really trying to do here. On the surface, it sounds like you simply want to create a JIRA server and use it to handle users. The steps there are simple - install JIRA, put the users into…
-
Ok, there's two parts to this. First, fix your workflow so that issues are resolved correctly. There are two basic options here: If your users do not care about resolution and don't want to use the field, then put a "update field" post-function on the "resolve/close" transition(s), setting the resolution to something…
-
I'm afraid the fix is to get your javascript injected correctly. Or better, stop using it, as it's probably the wrong solution to whatever you're trying to do with it.
-
Hi Andy. I'm sorry, I have completely misunderstood the problem. I will try again! >"While Developers resolved/fixed the issue they are updating the "Fixed in Build filed" but it's not displaying under details view. If we "EDIT" the issue and update the "Fixed In Build" value then it's displaying under Details View Tab. "…
-
Just to explain that __MSG__gadget comment in short (the doc doesn't really summarise it) - your JIRA needs to be able to talk to itself. It's as though the gadgets are running on another server. You get this error when the server that is running the gadgets can't reach the server giving it data. In this case, they're both…
-
It has a tendency to destroy your velocity estimations, and if you do it, it is well worth involving the stakeholders and product owners so that they know what you're changing and the reasons for doing so. It is all about the communication though. If you can point at a sprint and say "it went wrong because a bunny dug a…
-
Ah, ok. Start by forgetting the bulk-edit - that will work fine when you get the base permissions correct. To solve this, you will need to log in as an admin, go to the project that the issues are in and work out what workflow is in use for them. The project admin screens include a section detailing the "workflow scheme"…
-
A is by far the worst option, as you don't know how deep the bunny has dug, so all of your estimates, velocity and planning could go out the window B(1) is better, because you're at least tracking it properly, but still has the same problem of throwing all your numbers out. B(2) might be a slight improvement, and feeds…
-
The mail handlers built into JIRA can't do this. They cover summary, description, some of the user stuff, and priority in some cases. And they can comment. They don't look at custom fields. To handle custom fields, you'll either want to write your own handler add-on, or find one that can do it for you. I usually reach for…
-
Bulk edit is just "do something to many issues". It does not grant you extra permissions just because you are using bulk edit, it is just about doing something to many issues. The problem you have is that you do not have permission to perform whatever the action is on one or more of the issues you are trying to act on. Try…
-
The user got it wrong, but generally, it doesn't matter. They still see their request as before, and the agent can change the issue type to the appropriate so it still gets dealt with correctly.
-
JIRA Service Desk doesn't expect the request type to change, so it doesn't let the users do it. The Service Desk is a simplified front-end, with the issues being for use behind-the-scenes for JIRA users (agents) and not customers. The customers are not supposed to see the issue types - the point is that the request shields…
-
I am guessing, but I suspect you are using MySQL as the database for JIRA. If my instincts are correct, you are getting this error when emails containing certain utf-8 characters arrive. You should check your MySQL server is set up correctly for JIRA, but there's a known problem in that JIRA does not support the settings…
-
I think your "feature files" need some explanation. The Zephyr importer does import test cases for use within Zephyr, but you need to explain why it's not working for your files.
-
The most simple approach is the one you suggest, but you don't explain what the problem you are having doing it is? Set up space 1 with anonymous view access, and space 2 without it. That gives you a public and a private space. If you want to do this for parts of spaces, this is also possible. You need to make the space…
-
See https://developer.atlassian.com/jiradev/jira-platform/jira-architecture/web-fragments p.s. could you change your profile name to a real name? I think it made your posting be flagged as spam because the name was not real.
-
That is what my answer covered. Except I managed to leave out "you will do this with issue security schemes"
-
Workflows do not belong to projects. You need a workflow scheme to tell the project what workflow(s) it should use for each issue type. For the most simple case, create a new workflow scheme, tell it to use your new workflow for all issue types (i.e. the default) and then associate the scheme with your project.
-
Yes, although you will need to give it a "default reporter" if you want the field filled.
-
You'll need to find or write an add-on that implements a web-fragment and a container for the field. I'd stick with clicking "edit"
-
No, the Cloud URLs are fixed and can't be changed.
-
If it's failing to run, you need to work through the logs to find out why. The logs are quite noisy or verbose, and tend to give you a little bit too much (the "debug" information that is useful to developers, but mostly useless to the rest of us), but there's no way to work out a "can not start" problem than reading…