Comments
-
You need to authenticate the account - the link at the top of the error message tells you how to do this!
-
Start at https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html Extended Admin started a while ago, but I can't remember which version added the workflow stuff to it - 7.6 possibly, but it may be later than that.
-
* Jira can use webhooks and scripts in post-functions, listeners and reports to push data over to, or pull it from, Project Server (assuming it has a remote API you can use) * See https://developer.atlassian.com/server/jira/platform/rest-apis/ * See 1!
-
Sorry for the delay. What do you have for the board filter?
-
Yes. Without Apps, you can create a workflow for each issue type ((bound together by the workflow scheme for the project). Each one can have a different post-function for "Set issue field (priority) to <your choice>" added to the create transition. With Apps, you could write a script that looks at the issue type and…
-
I am sorry, but this does not make much sense. I can see you are trying to use Bugzilla and Jira at the same time (not ideal - Jira was written as a replacement for Bugzilla, so you will find it a lot easier if you just dropped Bugzilla), but that is all I can work out from your post. Could you explain further what you are…
-
I think you're in a "classic" project with a standard Software board. Rules only apply in "Next Gen" projects.
-
No, you have to licence each instance separately. (There is an Atlassian "Enterprise" scheme that allows you to have loads of users spread across several instances, but I'm not sure it includes Cloud and it's hideously expensive unless you've got tens of thousands of users)
-
You don't have admin rights if you can't re-activate users on that users "edit user" page. I haven't currently got site-admin on a Cloud system to check this, but I remember some talk about "if a user is completely deleted from a remote directory (or atlassian account), you still see their account for the history, but…
-
Diagram of what?
-
Yes, if you have Service Desk or Software, they are running on top of a Core install already. All your SD / Software users have access to Core as part of their licence.
-
You need to configure an outgoing email server (or service) to send the email. The email template function relies on your globally set email server.
-
They should hide when you're looking at the standard project list you see as a normal user (assuming the permission scheme does not include you somehow). As an administrator, you will always see the full project list when you go into the list of projects in the admin section.
-
I am afraid your question does not make any sense. You have not told us what the sides are, what you mean by flow, what stories and tasks are being moved or how.
-
I think you might be seeing the effects of https://community.atlassian.com/t5/Confluence-discussions/Changes-to-Confluence-Editor-release/m-p/1031058
-
This sounds like your Jira is behind an incorrectly configured proxy server. Could you confirm the setup of your system?
-
As an admin, go to Admin -> permission schemes and click "add". Find the line that says "Browse" and add either "all users" or "jira-administrators" and/or others who might need to see archived projects. Go into each project that needs to be archived and change the permission scheme to the new one.
-
Could you explain what this has to do with Jira? I think you've been directed to your organisation's Confluence (documentation) system, or possibly a Jira (request or issue) system, looked for help, and found a link to here for help. Problem is that this is for help with the system, not help with your organisation! We're a…
-
Cloud does not have archiving, only Data Center has it. For Cloud (and Server), you should set up a permission scheme that allows only the access to an "archived" project (read only, or admins only are the usual two choices), and apply it to each project you want to archive.
-
That would make the board completely useless. A board is supposed to help users work with a set of issues and show them where they are in the workflow/process. If it shows just issue type, it tells us noting of any use. I suspect you are asking for something other than what you have said - could you explain what you are…
-
Because "not in component" logically implies that there is a component to look at. When there isn't one, there is no useful answer to the question, so logic ignores it. So, when you're looking for "not something that can be described as X", you need to say what the "not X" is and also include "there's nothing to look for".…
-
That should be working. However, I suspect you may have run into a logical quick that's counter-intuitive (it's correct behaviour, but humans don't think the same way) Try changing filter B to component not in (some.component) or component is empty
-
The script needs project_key and scheme_key replaced with the IDs of the project that is broken and the scheme you want to swap it to.
-
Jira Service Desk and Jira Software are "applications" that run on top of Jira Core. If you are using any combination of the three, then you have Core already and adding Software and/or Service desk to that is the best way to extend or integrate them.
-
Ah, sorry, I misunderstood. It's not possible to do this - the fields in there are fixed by the layout code. Have a look in the marketplace for extra reporting Apps though.
-
Yes, I think so. I think a lot of us get them mixed up, I know I certainly did when I first started needing to do checks in workflows!
-
You can paste any licence into the licence box, even expired ones. You can get your history from your my.atlassian.com account.
-
You'll need to explain what this has to do with Confluence?
-
Yes, the agents who can configure your project/service desk can add new request types.
-
You can go to your my.atlassian.com account and ask for an extension to an existing trial.