Comments
-
Doesn't seem to want to open, sorry.
-
There were four up there a minute ago! I think it's time to talk to the neighbours about better fencing. Or maybe not, we all like eggs in this house...
-
Is this a migration (just moving from one server to another), or a merge (existing projects in the source will be added alongside existing projects in the target)?
-
There's not a lot we can tell you without looking at the logs. A line of generic error message is a start, but it is very rarely enough to pin down the actual problem.
-
What does the board's sub-filter say? The default for Kanban is a look at fix versions. Does your second issue have a fix version?
-
You'll need to read the log file to find out what the full errors are. See <jira home>/logs/atlassian-jira.log
-
Then what Joe says. Export and import is a total waste of time. Bulk edit to change the "account" on the issues, and maybe again if the issues need to move project as well.
-
At the moment, Data Centre can only be installed in one location (all nodes in same physical data centre). Atlassian are looking into geographically separate nodes, but don't yet support or recommend it.
-
This is built-in. Use the post-function "set field", setting "assignee" to "none"
-
There's an implied "If you stay with the Cloud product" in the discussion. Rest of what you say, I'm broadly with you, on the Cloud side. I kind of see where they're going across the range of products, but the Cloud UI is broen, and there's not enough action trying to make it usable happening (I'm not even sure it can be…
-
The code you've given is nothing to do with the REST API, it looks like something that sits in front of it. The REST API expects a command or JSON. So, forget it, it's a red-herring. What JSON are you sending with the put?
-
6.6.6 is not "the most stable", it's flagged as the Enterprise release, which means long term support and patching. 6.8 is more "stable" (depending on what you mean by that word), and includes some (minor) stuff around performance too.
-
You would have to ask the person who set it (either the person entering the issue, or what they configured in the automation/post-function/listener)
-
That's not the REST API, that looks like some form of library that sits in front of the REST API and provides some coding layer over the top of it. The REST API would expect an http(s) "put" with a set command embedded in some JSON. So, which library is it? JRJC?
-
You will need to find or write a more advanced "email handler", one that can parse your incoming email for the data you are looking for and add it into the right fields. You could write something, but I usually reach for the JEMH app, as it's far more configurable and flexible than anything I've got time to do. See…
-
I don't have a way to do it either. And I can't recommend it because it will render your field inconsistent in behaviour - in some places it will default to h in others, m, for the same user in the same project. That is a really bad thing to do to your users - ask them to remember that sometimes you need to do things…
-
Ok, great. That narrows it down to one of two things: 1. The reporter field is on screen, the user creating the issue has "change reporter" permission, and they have used it. Note that when other people try the same, if they do not have "change reporter", they won't get the field. That applies to you as an admin too - you…
-
We might have a new pet. She moved in next door, but seems to want to live with us (this is an unusual sight in town centres in the UK by the way) Needless to say, the cat is not impressed.
-
To save your testing - you're right, the IDs of things not in the workflow (i.e. transitions) will change. They have to, as the target Jira will not be in the same place as the source and could easily have the incoming ids. It treats all the incoming config as "new".
-
No, web fragments and scripted fields are two totally different things. A web fragment is part of the ui - menu items, panels, buttons, etc. ScriptRunner allows you to add your own, so you can add to the UI. Most of us use web fragments to trigger scripts, or add information to a screen. A scripted field is a field that…
-
I am not sure, you have not confirmed that my description of what you are seeing is correct.
-
This is not something you can do with a behaviour. Jira's default time settings are done internally, not on the front end. You might be able to inject something that can look at a number when it is entered and add an "h" if it is left blank, but it's only going to work in some places, which means your users are going to…
-
Sounds like the site shuts itself down during the space creation. What does the log file say is going wrong? Look at <confluence home>/logs/atlassian-confluence.log first, and have a quick look at the other files in that directory. If there's nothing in there, check also <confluence install>/log/catalina.out
-
java.lang.OutOfMemoryError: Java heap space is a smoking gun. The system has run out of memory because you have not allocated enough for it to function. You need to increase the amount of memory for the heap - this is the -Xmx setting in the environment I don't know quite enough about your set up to be precise about where…
-
What does "stuck" mean? Tell us the symptoms (we can assume "stuck" means "Jira not appearing to do anything else", but what is on screen?). And what does the application log say (look at the last couple of hundred lines at the point at which you get stuck)
-
I think we need more context for the question. The question is probably fine, but out of context, it does not make sense. * What does "get" mean here? * What "interface"? The ui elements, the class in the internal API, the data from REST? * What "custom subsection"?
-
I am sorry, but the question does not make sense. >my issues is added task on sprint will start , then on going task it was on priority basis My best guess is that you create a new issue (of type task), and then move it into a sprint, which you then start. I cannot work out the rest of what you are asking.
-
No, that's the wrong approach. A transition is there to change the status as an issue moves on through the process. You do not want to change the status if conditions are not met. Your "post functions" are not the right way to do it. They are really actions you should be taking before even looking at a transition. Once…
-
You will need to change the email on the NEW account to something else (log into id.atlassian.com with it and go to the profile settings) Then do much the same on the OLD account - log into it and change the email to the new email.
-
It happens when you create a workflow from scratch - Jira doesn't know what events you might want to fire, but it has to put something in, so it just picks "generic" for everything.