Comments
-
Ok, that makes sense. A 413 error means "whatever the http(s) stream we are handling, it is too big". Most browsers do not have any code to do capping that would cause a 413, but web-servers all do, and most set a limit by default (to prevent load and overloading attacks by default) Your nginx server is the culprit here,…
-
There is no expectation of it going away. If anything, Atlassian are increasing the numbers and support.
-
Nope, no other reason. It's a design flaw. It only affects administrators, and only those who have inherited poorly designed workflows built by inexperienced admins. That's probably less than a "small handful" of users to be honest, or at least should be, as the biggest mistake people make with Jira is "too many admins".
-
This is exactly what is says on the tin. The Jira user (the windows user the Jira service is running as) does not have full read, write, execute delete rights to the home directory you have defined. However, your question is a little unclear. You say "copied home directories to second node", but have you set it up…
-
Status is changed by running a transition on the issue. If you want to change the parent issues, you'll need code or a script that can trigger the transition you need to do on the parent. I'd strongly recommend using a listener for this, and it could be complex, because it's going to have to think about every possible…
-
Nearly. Look at the latest 7.12 Jira release. Project admins have more power over the admin of a project than they used to - they can change workflows and some field options. Issue types, no. But as issue types are structural and essential to defining shared processes in a sane way, you almost certainly don't want project…
-
Edit the workflow, and amend each "OUT" (of closed) transition. Add a post-function to each, selecting "update issue field", select resolution, and then none for the value at the top of the list. When saved, it should display as "resolution will be cleared"
-
We'll need to see the logs for the time at which the errors occur.
-
You can set that up easily with permissions. Make sure the permission scheme for each project only grants access to the unit who should use it. With careful admin (and getting rid of Atlassian's default "anyone with a login gets access to everything"), you can completely isolate projects into silos. The things you can't do…
-
The documentation is wrong, it's Jira and System admins only, board admins can't do it.
-
Next to the name of each app, there is an "expand" > Use that to expand the area and see the version
-
It's not a case of not needing it. You do need to see the order. But you'll have to do it with a relative script that is for display only, and will change by context (apparently randomly at first glance) "Simple" numeric ranking at a global level increases the work any re-ranking work exponentially by the number of issues…
-
Ok, the first screen suggests that you are not a Jira Administrator - you need to be at that level to be able to change the type of the project. You'll need to talk to your site admins to get Software removed, although you can partially remove bits of it for users by denying them access - change their groups so they only…
-
You can't do it. See https://jira.atlassian.com/browse/CLOUD-6999 for the request to enable it. Some people claim some measure of success with effectively proxying and rewriting it, so when you land on xyz.org, it simply asks xyz.atlassian.net for the data and passes input back to it. But this is horribly complex if you…
-
Ok, that's definitely something you should be looking at an App for. I mentioned the one I've used (so I know it can do a lot of that) - https://marketplace.atlassian.com/apps/1216711/refined-theme-for-jira-service-desk
-
You'll need to explain "cannot change, just delete" and why you "cannot find" the function to remove Software. Could you go to the EM3 project, select project settings and look at the top panel in the admin column, it has "delete project in it". On the Software removal, go to Admin -> Applications, find Software in the…
-
"Change" is very vague here. If you mean you want to add fields to it, to get more structured information, yes, you can map fields from the underlying issues in the portal/request definition. If you mean changing the layout, then not off-the-shelf, but you can do things with Apps - the only one I've used for "theming" a…
-
Depends on what you mean by "multi tenancy". It certainly supports different organisations using it and segregating their data, but if you mean "having many totally separated services for different sets of people", then no, you need to install many separate services.
-
That's the add selection, not the display of who currently has the permissions.
-
A "de-simplified" workflow inherits the name unless an admin remembers to rename it, so you may be looking at a non-simplified workflow that has a misleading name. Or, you are not a board admin. System and Jira admin rights give you rights to admin the system, not do everything (very bad security model).
-
I'm not sure how "go into each project and change the type" is not easy when it's just a simple dropdown? Nor how clicking "remove" (or just "disable") on an installed application is not easy?
-
Go to the project and change their type to Service Desk or Business. Then remove the Jira Software application.
-
Sorry, I missed the follow up! I suspect the problem is the link from Confluence to Synchrony, not Synchrony itself (I think it's sitting there waiting for a call from Confluence). Could you look at the Confluence log for a time just as you open a page for edit? (With collaborative editing enabled)
-
Start at https://scriptrunner.adaptavist.com/latest/jira/behaviours-servicedesk.html
-
That sounds like a broken index! Could you try re-running the filters, note how many issues each one returns (don't worry about the content, just numbers), then re-index the project and re-run and not if any of the numbers change?
-
One of your admins changed their project's "workflow scheme". You might be able to find out who from Admin -> Audit
-
You should be able to just paste the key straight into the key box and it will take. If it's the wrong shape, or for the wrong product, generally, you won't get the error message you have got here, you'll get a useful one. In this case, you need to do what it says - read the log to see the details - <jira…
-
Yes, that's because you're getting existing data before it is updated. I don't understand why you are trying to get it at all, when the post-function has direct access to both old and new data.
-
Hmm. I'm not sure that they are coming out in different formats. Could you pick two of the issues above (from one column) - one where you think it's output month first, another where it's done day first. What does the date column say for both of these when you look at the issue display?
-
There's no point telling us not to blame the database. It is known not to work properly. Move to a supported database, and try again.