Comments
-
Admin -> Resolutions, for the list.
-
It means you have broken config for an add-on, or there's a bug in it. The add-on is https://marketplace.atlassian.com/plugins/eps.focuspro.EasyDropdownMenu/server/overview if that helps.
-
Most of the statistics gadgets require bounded fields - ones that you can be certain you have a limited set of values for. Text is not one of those fields, it could have a vast range of totally unique values, rendering it pointless as a statistic.
-
Good spot on the workaround, and it answers a question I was going to ask. You've not run into the problem I had with Turkish, as that was an external user source with incorrect Jira collation - Jira lost the accents and then couldn't find the user in the directory, even though it was right in the database (the collation…
-
You are going to need to give us more context. Jira field options? Status? Post it notes in your house?
-
Assuming you have edited the workflow so that it has a status of "Ready for Review" and you've got appropriate transistions for it, then just put this status in the "done" column on your board.
-
Same answer.
-
No, Jira's security only goes down to the issue level. You can only protect the whole issue, all of it, or nothing.
-
Ok, that makes more sense - it's not a conversion of incompatible types, you want to work out a date given another date and a length of time. You'll need one of the scripting or automation add-ons to do that calculation. However, be prepared to jump through some hoops - you may need to think about weekends, holidays, etc...
-
The recommended method is to use the Active Objects layer built into Jira. I've seen external databases connected to, but not really for holding Jira data - they seem to be too slow and unreliable, and you can't pull the data into Jira proper without writing entire DAO and Jira integration plugins, which you can usually do…
-
That is correct. Cloud uses nothing but "external" accounts now. Google accounts or SAML based ones are controlled in their respective directories. Atlassian accounts belong to the users, not the administrators or the organisation. Users can change their full name on their account, but random admins can not because it's…
-
Yep, it's up to the agent to deal with issue changes on the base of what the customer says in comments.
-
Jira doesn't have features like that. The project doesn't have a field to store that or a way to mail you when it changes. I've seen it done with "a project of projects" and some scripting.
-
That is correct I'm afraid. Jira Cloud has the right model - an extra global permission for a group to be able to create projects without being admins, but I'd take Dave's comment as gospel, it's not going to server for the foreseeable. (This product divergance is getting really annoying)
-
Customers raise requests, not issues. The issues live behind the Requests in the background and are for Agents and participants to work on, not customers. To give a customer edit access to the issues behind their requests, you will have to grant them full Jira access and make them a participant.
-
Ok, so you can't assign at all. Assign to me will only appear if you can assign issues AND you are on the list of assignable users.
-
Start at https://developer.atlassian.com/server/confluence/writing-confluence-plugins/
-
Please raise this as a support request at https://support.atlassian.com/contact - we're end users here, not full support, and Dario may not see or get to your question as fast as you'd like. Support will see it faster. I know you can have an instance on the Irish data center. I don't know if Atlassian will move it for you…
-
We can't debug this either - we have less access to your Cloud system than you do. We're end-users of Atlassian stuff like you are, and I'm guessing you have a "starter" licence (10 users), so you've landed here when asking for support, as Atlassian don't do direct support for starters. I can't replicate it on the Cloud…
-
Are you the reporter or in at least one of those three roles? That permission gives you the right to assign the issue. It gives you "assign to <someone>" rights. But it does not mean you are on the list of possible assignees. Take a look at the other assignee permission, which defines "who can be assigned an issue" - I…
-
Duplicate of https://community.atlassian.com/t5/Jira-Service-Desk-questions/Getting-error-while-create-issue-with-environment-field/qaq-p/760422 which has the conversation needed to answer this already started.
-
As an admin, create a new "screen", adding just the "assignee" field to it. Edit the workflow for your project. Find the transition from resolved to re-open. Look at the definition for it, you should see "Screen: none" - change that to your new screen. The comment field will appear as well as assignee, if the user has…
-
There are two options for Confluence pages really: 1. https://confluence.atlassian.com/doc/configuring-a-webdav-client-for-confluence-148044.html - it will let you do the basics, but you won't really be able to use the full power of Confluence, unless your system can hook into the collaborative editing, and fully…
-
You will have to give them rights to work with the tools. This could mean allowing "anonymous" access, which means they don't need to log in, but should be restricted to read-only (otherwise you have no control over or visibility of who can mess up your system and will be spammed if it's on the internet), and that means…
-
Ok, when you say "documents", do you mean Confluence pages, or Confluence and/or Jira attachments?
-
Can they create issues in the projects? Do they get a "tried to perform an operation they have no permission for" error, or "You do not have permission to see this issue" error when they try creating an issue?
-
What do you want from "integration"? What are you trying to achieve?
-
They run a Jira system for their users. I can't really tell you a lot more than that, with such a vague request. https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html might help you a bit, but the job in general does really mean "making Jira work for your users"
-
Atlassian Cloud takes all that away from you. You only need to worry about doing internal admin of the applications (users, project setup, workflows etc)
-
If you've got a "starter" licence (10 users) then you get directed here because Atlassian don't really support them any more. They refer starter users here, which has its good and bad points The bad points: * They may be ignored if the question is not that interesting to us, or they're poorly written, angry or could have…