Comments
-
Yes, but you will need to work through the permissions structure. Your customer group will need to be granted access to see all the spaces you want them to see pages within. You will want to be careful not to let them see any other spaces. Once you have that right, you may want to think about restrictions within those…
-
Where are you trying to add this group in the global permissions?
-
Correct, it cannot be changed on Cloud. There is a request open for this, but there is no timeline. Atlassian have not closed it, so they are not saying "no" yet.
-
Can you check your project's "issue type scheme". Specifically, does it have any sub-task types listed? Also, the "create issue" process will not offer you sub-task types. You must be in the parent issue to create sub-tasks.
-
It looks at the history for when the sprint field was updated.
-
There is no "merge" of JIRA users I'm afraid. You will need to do some hacking to do that sort of thing - bulk changing reporter and assignees will fix some of it, but any comments that have been made will need to be hacked (to change to the "right" account) or deleted. This is quite a difficult one to fix to be honest.…
-
Yes. An add-on licence must match the number of users you have for the product. JIRA 7 has made this a bit more complex, but also cheaper. Imagine the case: * 5 Service Desk Agents * 100 Core users * 50 Software users You have up to 155 users. But the add-on only needs to be licenced for 100, not 200, as the rule is "the…
-
The easy answer is "add a new status in the admin section and then use it in your workflows". Because that does what you seem to be asking for. I think there's a missing piece of question somehow. I don't see what "with the same functions as ..." means. Could you explain that?
-
I do not understand this question on two levels. I am ashamed that I do not speak anything other than English. But when translated, your question is about sharing reports. JIRA does that for filters, dashboards and so-on, you just need to go into the definition, and make it available to the people who want to see it. So, I…
-
You don't. Because the end-user should not care who it is assigned to. The current agent who is talking to you is good, but exposing the assignee is usually a really bad idea. Simple case - Alice asks for support. Bob the agent talks to Alice and thinks she's found a bug, so Bob asks Charlie the developer to fix it. Do you…
-
Start with a run through https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html as this covers most of the "plugins not started" errors.
-
Thorsten, you should be aware that "we've introduced a more robust, flexible exporter in the CSV export" is incorrect. The CSV exporter is not robust or flexible, and the clear consensus from users is that it is not a viable replacement for the Excel export yet. Until it meets the minimal functions that the Excel export…
-
This is a very specfic semantic point. Reporter = person who reported the issue Reporters = the people who might report an issue When you use "reporter" in the permission scheme, you are not saying "the person who reported it", you are saying "anyone who might report an issue", or in other words, "anyone who can create an…
-
The link has had punctation added to it. I do that all the time - end a sentence with a link, and then add a full-stop to the end of it for correct grammar, which then breaks the link. Try removing the %C2%A0 from the end. I've posted this long explanation because there are quite a lot of links with similar problems here,…
-
You can't do it. The feature was removed in favour of the CSV export. Spreadsheets can all read CSV, so the idea is that if you needed Excel, you can just open the CSV. I'm afraid, on Cloud, you are stuck with CSV, unless you can find an add-on in the marketplace that can replace the functions. (Personally, I don't think…
-
It is a good test to disable the collaborative editing - the admin flag for turning it off it is still there in 6.1
-
Which profile are you looking at?
-
Yes. Also happens when you try to add a tag - you enter "JIRA" and it's pot-luck which "badged" tag you get.
-
Yes - a simple REST call from your dashboard application can return all the data from the issues on your board, in a format ready for your dashboard to easily reformat for display.
-
The most likely explanation is that the Tempo add-on is disabled for some reason. Can you check in the list of add-ons what its status is? Look specifically for an error, the "disabled" flag and its licence status.
-
I think this is the same as https://community.atlassian.com/t5/JIRA-questions/How-to-view-read-only-workflow-in-Customer-Portal-page/qaq-p/583819
-
Vishnu is right, customers don't get to see the workflow (because it's not necessarily the one they will seem to follow, and frankly, they don't need to know what the process is if you've got it set up right) You can give them the option to perform transitions on their requests though. See…
-
No, 6.2 to 7.3 is not going to work, it's too large a jump around a major upgrade. There are three upgrade routes I might look at * 6.2 -> 7.0 -> 7.3 * 6.2 -> 6.4 -> 7.3 * 6.2 -> 6.4 -> 7.0 -> 7.3 If your installation is simple and has few or no add-ons, there is a good change route 1 will work. If testing that shows any…
-
What date field is the calendar based on, and which calendar is it? Can you check the date shown on the issue?
-
You can not change the base url of a Cloud instance.
-
Disable their account, and then re-enable it when you're ready?
-
This is what it says it is - it can't connect to the database, because the database server does not appear to be there. The TNS error is telling you that TNS is not set up to route to that database, (or possibly allow connections), so you need to fix that and try again.
-
Duplicate of https://community.atlassian.com/t5/JIRA-questions/Is-that-correct-that-only-the-developer-need-to-use-the-Service/qaq-p/583483
-
You'll need to raise this with support over at https://support.atlassian.com
-
Ok, so the user is jira, the data directory is owned by jira and the owner permissions are rwx, which is correct. My next guesses are: 1. SELinux is interfering with file access 2. Your attachment directory is a remotely mounted file system (NFS or something, so you can store attachments on shared disks to allow for…