Comments
-
.obr files are add-ons for Server, not Cloud. You cannot install those on Cloud. That add-on does not have a Cloud version yet, you'll need to look for something else that does the job, and has a Cloud version.
-
Confluence is not a web server that renders up arbitrary html. Your file is an attachment and hence gets treated as an attachment. If you want to render it in Confluence, you'll need to convert it to a Confluence page, or find/write a macro that can read and render an attachment.
-
All the docs and guides are similar, as the access model has not changed hugely since Jira 3.6 The one big change was the defaults in JIRA 7.0 - instead of having a "jira user" group grant login and some project access by default, the groups changed to three "can use application" groups. This does not significantly change…
-
Again, your code does not appear to log in, so it has no permission to do things.
-
One of your administrators has made the "assigned to" and "due date" fields mandatory in that project, either with field configurations or with validators in your workflow. You'll need to undo that change, or probably limit it to the project(s) where they intended to do it.
-
If you turn off collaborative editing and still have issues, then it's nothing to do with Synchrony. Whatever the issues are though, we really can't help you unless you tell us what they are.
-
Your url is wrong. You've got control characters encoded into it which should not be there. Try OT-1400 on its own, not %7bOT-1400%7d
-
>Archived issues are searchable but they don't show up on boards Create an "archived" status in the workflow and exclude it from the board filter. The reason it's not "built in" is given above - there's no clear definition of what an archive would be yet. Atlassian took a stab at it 5-6 years ago and ran into so many…
-
What does the log say the problem is, and what are the other fields on the create screen?
-
You can't "hide" an issue type. If you don't want to use one in your project, then you have to remove it from the scheme, and migrate any issues of that type to another one that you are not removing. You can, as Joe says, hide the issues of that type with a security scheme, but your users will still be able to creates…
-
That is the problem then - what are the errors?
-
Your browser is not getting or rendering the css and javascript Jira is giving it. There's a couple of things on the server side that can cause this, but it is usually a browser or network issue, and as you are on Atlassian Cloud, I know it won't be the server side. Check your firewalls and networks, and have a look at the…
-
Click the drop-down arrow at the top right and select "edit" from the menu. However, I suspect when you say "edit", you mean "completely change the gadget" - if that guess is right, then the answer is that you'll need to find or write new add-ons that provide gadgets that do what you need, not "edit" existing ones.
-
A filter does not have the information required for generating a burndown chart. You need the sprint information as well as the issues, and as sprints are part of boards, you therefore need the board.
-
You probably want to do a full xml backup of your source system and then use "project import" to pull the issues you want into the target.
-
The new layout for Cloud is unlikely to make it to Server before the next US Summit.
-
See https://confluence.atlassian.com/adminjiraserver074/migrating-jira-applications-to-another-server-881683277.html
-
You need to raise this with https://support.atlassian.com/contact - we need to read the logs, but only Atlassian support have access to them on Cloud
-
Go to my.atlassian.com, log in and go to the list of licences.
-
What does the log say the error is?
-
It can be a duplicate in the xml as you say, or trying to upload version x.y.z of an add-on which is already installed at version x.y.y
-
It would be useful to find out if others have this problem. As a developer, it is often useful to have many bug reports from users in different situations. I've also re-read that answer and I want to add that the problem may well not be Centrify. The error is happening in their code, which suggests a bug in there, but it…
-
The updated logs tell you the problem - you're trying to install an add-on manually that you already have installed. "com.atlassian.plugin.PluginParseException: Found duplicate key 'new-cf' within plugin 'com.dnfcs.jira.newCFType'" Try removing the old version rather than upgrading or installing it again.
-
Have you tried reading the documentation for the add-on?
-
The error message you have given us points to a bug or problem in the Centrify code. There's not a lot we can do here, other than ask them to explain it.
-
Change the server ID in your my.atlassian account, and it will generate a new key for you.
-
The emails on Lithium are very poor, with random duplicates being sent, and often the mail (original and duplicates) suffer several hours of delays.
-
Place the field on the right screens. https://confluence.atlassian.com/jira064/configuring-fields-and-screens-720412098.html is a good guide, and still holds true for Jira 7
-
Yes, that is what I said. You can use markup. You cnnot change the renderer. Different things.
-
Jira is not intended or designed to be used in frames, and it mostly just doesn't work when you embed it. There is not a lot you can do here, it is broken, it's going to stay broken, and your best bet is to create a dashboard in Jira (or Confluence) and get your boss to use that instead.