Comments
-
It's often in the footer of the pages, but if not, it is available in help -> about. As I said already, the API is always on in later versions.
-
If your Jira is of a recent version, there's nothing to check - the API is always enabled (because parts of the system require it). I think the option to turn it off was removed completely in 6.4. If you are on an older version, where they can be disabled, your admins can check by looking in general configuration.
-
Where are you changing the avatar?
-
It means that Crowd cannot be reached by bitbucket at that time. This is more likely to be a network or crowd error than Bitbucket, as you know Bitbucket is actively trying to authenticate someone (i.e. working). Do the bitbucket logs say there is a specific error in the connection, or is it just "not reachable"
-
No. You can not write to a Jira database while it is running. At best, you'll corrupt something making bits of it unusable, at worst, it will become totally unusable and you'll need to go to the last backup. Your best option at the moment is to set the automatic assignee as per your needs and leave it work as it is.
-
You cannot know who the "automatic" assignee will be until you commit the issue so that the code can work out the person who will be assigned. I'm afraid that code is in the "create issue" process, not the screen, so Jira can't tell you the answer. Your only option is to read the rules for the components and work it out…
-
I'm afraid authentication failed is a simple one with three possible causes: * You are giving it the wrong credentials * You don't have an account there * The authentication system is broken on the server side. It is working for me at the moment, so I doubt that's the problem. You can test it by creating and logging in as…
-
Have a look at the project permissions. In there, there is a rule for who can "browse project". You need to make sure that your user meets the rule. Ideally, the rule will be something simple like "Role: users", which means you can add them to the project as a user and that will get them in (without granting them access to…
-
Issues = things that need attention Projects = logical groupings of issues
-
Which application is this in?
-
You're repeatedly ignoring me, so there's no point in bothering responding to you any more. We'll just have to agree that we have different opinions and go do something useful (you could, for example, write a custom field that behaves the way you want - base it on the multi-select code which is already 95% of what you are…
-
It does and it doesn't. Jira Core does it. If you put estimates of time on sub-tasks, using the original estimate and worklogs to indicate what has been done, then you will see that there is a tick box in the estimate panel on the parent that says "include sub tasks". This toggles the panel between showing you the estimate…
-
<sigh> I really don't think you've got it. Most people want free-access. Those who don't already have the option of multi-selects which fulfil most of the requirement, and work for the overwhelming majority. Most of the people who are asking to limit labels are just not understanding that what they're asking is already…
-
You can, but my limited understanding is that you will need to make sure your machine has a consistent host name (meaning you can't use the ip address if it's a laptop that moves between networks, or your internet connection doesn't have a fixed ip address)
-
I think you answered your own question - use a url field.
-
This is the same question as https://community.atlassian.com/t5/Jira-questions/How-to-determine-the-value-of-drop-down-options-and-compare/qaq-p/784306 which has an answer.
-
The only method of getting the old UI back now is to migrate off Cloud and on to Server. You can't go back on Cloud.
-
Chris, I'm railing against people who don't read what I've said, and those who to refuse to grasp that what they're asking for is (mostly) possible already. I'm not confusing "right" with "current implementation". I'm explaining that you already have access to a "right" option, although it is not as good as it should be.…
-
These are not things you can just state, and even if they were, they're not things the software would state. These are goals that should be set by your users. Imagine I've got a couple of clients using the Atlassian stack who are thinking of recovery in the face of a problem (I've got way more than "a couple", but I'm…
-
Please, stop ignoring what labels are for - they're supposed to be free for the users to enter what they want. If you need to control what they enter, then use a list that restricts them. It's not Atlassian being arrogant, it's you not understanding what a function is for. At the moment, controlling a field's options means…
-
You have got it spot-on. A security scheme defines a load of "levels" which then control visibility in clever ways, but when you look at an issue, the only data on there is "the current level". Jira does put some thought into it when you apply a new scheme but it's hard to explain in general, so here's an example instead:…
-
How are you checking the mail box is empty? Some clients play tricks with layouts that make you think a box is empty when it technically is not. Have a look with a basic client - most webmail systems will do it if you want to avoid installing anything new - email.com for example
-
Never put the resolution on a create or edit screen, and certainly never make it mandatory (and you don't need to worry about making it mandatory on "close" of your issues if you use it on a transition screen) It breaks your data instantly when you do that.
-
You can only "edit" the issue type when the config is identical for both types (fields and workflows basically) You should find you can still use "move" though. Keep the project the same and "move" to a different issue type.
-
There are a couple of apps that can help a bit. Have a look in the marketplace. The most simple one is pretty much a combined search, which most of the apps do in some way.
-
You need to make sure you log into Cloud and the licence site with the same admin account that owns the site and has access to add-ons. The error message suggests there's a disconnect - it can't work out which Cloud site you are trying to licence.
-
No, it's not possible, and I think you've already intuited why - transitions are more complex then simple edits. It's easy to make an edit part of a transition (the transition screen), but transitions are a whole pile of things - conditions, validators, post-functions, triggers etc which don't naturally happen in an edit.…
-
That's not what my Jira systems do. I get project role notifications. When you say "add project admins to the notification scheme", are you sure you are setting the role and not a group?
-
Go ahead and remove the users. The role itself is global, but it's there to identify users and groups *per project* For example, you probably have at least the default roles of user, developer and admin. I can be admin and developer in project 1, developer in project 2 and user in project 3. The roles go across all…
-
Hmm. Well, there's no errors in there to say why it's not running either. How long have you given it to start up?