Comments
-
Have you tried the "where's my field" option towards the top right of the screen?
-
Hmm. Could you pick one of these issues with [nul] and show us the issue details? Specifically a screenshot that includes the full key, summary and type of the issue (we don't need to go to the description, it's the headers we need)
-
No, a single JIRA install has one "theme" in terms of branding. You can do things like different icons for projects, and all users can choose whatever home they like.
-
Is this a Connect add-on?
-
This is what a "cascading select list" does.
-
There is no way to restore a deleted account. That's why we recommend disabling them instead.
-
It's the same answer. If a user can see a project, then the permission scheme for it says "This user has browse permission" in some way. Same for Create, and the other permissions. You need to remove the permissions that let the wrong people do things. Remember these are not direct. You could say "Browse: Alice, Bob and…
-
That should work, as you'll have a group context for the user!
-
I'm afraid when it comes to logical breakdowns of work, it does not make sense to have a sub-task have two parent issues. They're supposed to be there to break up the parent, which they can't do if they are part of another. The best way to handle it is two sub-tasks, and link them together with an issue link.
-
The server does not need access to the internet. You do, so you can get the licence key. But once you have that licence key (it's an encrypted block of text of a few hundred characters), you can paste it into bitbucket.
-
Sub-tasks are issues in their own right, and their events and mails are no different to any other issue type. You say > "the values of the fields that make up the screen of that transition" That's not what emails abased on events do, the fields on a screen are irrelevant, the emails can access all the data on the issue…
-
No. Yet again, you have not bothered to read the previous answers. The "tormented" happened because the wrong question was asked and it took some time to get the questioner round to understanding it. I explain things when a question is asked in a way that implies someone needs things explaining. Your questions show that…
-
Issue type is not a field (so line 3 is wrong) and when you fetch the object, a simple comparison to a string is never going to work. Try if ( "QA".equals (issue.getIssueTypeObject.getName()) ) instead
-
It's very simple - go to the permission scheme and look at who has permissions to browse and create. Change that so that it says something like "role (the-users)". Then remove all groups and users from that role in the project, apart from those who should be using it.
-
Again, it is not a copy. There is only one sprint 1.
-
It's not a built-in function, so one of your administrators has disabled or removed the add-on providing it. If you are on Cloud, that would be consistent with Atlassian's gradual removal of some of the standard add-ons they're trying to get rid of (Misc Extensions, JIRA Suite, Toolkit etc)
-
Cloud uses "external management" automatically. You can't amend users and groups in JIRA on Cloud, and that's why your REST calls are failing. You have to do it via Cloud user management which you can get to through the JIRA admin UI, but it's actually a separate system. That does not support REST calls for updates (yet -…
-
It does support MySQL - see https://confluence.atlassian.com/doc/supported-platforms-207488198.html for versions
-
I think you've added the attachment to the issue, rather than the request. Therequest is what the customer creates and sees in the portal, the issue is the underlying data behind it, available only to agents.
-
Go to your my.atlassian account, and find your licence for Bitbucket. You can copy the key to a clipboard and then paste it into Bitbucket when you get to the licencing screen.
-
It's "tormented" because the original question was not the actual question the poster had, and it took a while to get the actual question out of them. Still, we got there in the end. The answer to your questions are "an issuekey is always <project>-<sequence>". There was no search for a range of numbers when the original…
-
Stop all the Atlassian applications on the machine, then check the lock file is definitely gone, then try again.
-
On Cloud, you can just add more until it tips over into the next band. On Server, go to your my.atlassian account and get a licence for the next tier - it will take into account your current licence.
-
Try adding a "cascading select list" custom field.
-
A minor point - there are a number of add-ons for Server that do not function properly on data-centre (mostly down to caching stuff). If you're considering a more to DC, check your add-ons.
-
Boards don't belong to projects. There is no way to group boards together I'm afraid, other than giving them logical names. It would be nice if we could, and I think there's a feauture request somewhere that has something like "board categories" similar to project ones.
-
So what does catalina.out say now?
-
>There is no valid reason to not allow someone to delete their own subtasks against which no time from another user has been logged Absolutely wrong again. You really need to read through the reasons above properly. There's a difference between your opinion and reality.
-
Yes, you did. It's understandable, and an easy mistake to make. Bahmni is using the Atlassian stack to provide their docs and/or issue tracking, and you've clicked on the help links for the application they're using for that, rather than the help for their products.
-
It's not broken, so there's no workaround. You need to write some automation code to do this.