Comments
-
I've found organisations are very weak on their support for the standard .invalid RFC. Bad, I know, but we live in a world with Internet Explorer to which "standard" is something to be comprehensively ignored. I cheat and talk to the email administrators whereever I go, asking them for an official "null" email address to…
-
I've found organisations are very weak on their support for the standard .invalid RFC. Bad, I know, but we live in a world with Internet Explorer to which "standard" is something to be comprehensively ignored. I cheat and talk to the email administrators whereever I go, asking them for an official "null" email address to…
-
Service Desk customers have been free since Service Desk 2, but only for the JIRA part of the Atlassian stack. Atlassian promote Confluence heavily for use as a Knowledge Base to work along-side the Service Desk. You will need to buy Confluence and licence it for people who are going to write your KB articles. Before…
-
The application log file should tell you more about the "connection refused" error. If you've ruled out the actual settings being incorrect as you copy them into Jira, then you need to start looking at ports and firewalls (yes, even for a local machine)
-
Whatever you mean by "post call", it's not logged in as a user who has the rights to create the issues, so you need to fix your call so that it logs in correctly.
-
I assume by "system", you mean Jira? You'll need to find or write some code to do that - it's not one of the off-the-shelf reports (and it seems quite specific to your site)
-
Ok, what else can you do to the issue? Can you edit it at all?Also, is Resolution: Unresolved showing the "Unresolved" in italics?
-
They're usually in a state that means voting is of no use (closed)
-
Make sure the assignee field is on the edit screen for that issue type, and that the user has "assign issue" rights in the project.
-
I haven't looked! I'm not monitoring it - most of our clients haven't upgraded yet, and I have a tendency to wait until my favourite add-ons are upgraded.
-
Ahh, yes, I admit I've not kept up with compatibility. The Toolkit should be done soon though - too many people rely on it in Cloud, so there's pressure to get it updated.
-
Have you got the right version of the "JIRA Toolkit" addon installed?
-
Could you tell us what version of Jira you are using? Either the version of your downloaded software, or just OnDemand if that's what you're using.
-
It's about human behaviour and simplicity. If you give a human the option to do something, you need to tell them why they can't do it if you then block them (so validators have feedback) If you do not offer them the option to do something, then you don't need to explain why you are not offering it to them. You wouldn't…
-
The other option is a validator - let the user into the transition, don't use conditions. Then when the user tries to commit it with invalid information, they will be returned to the transition screen with an error message explaining why they cannot proceed. Udo's suggestion is really good if you want to block the user…
-
You also need to delete the issues. You've spotted the change history and workflows, but you would also need to deal with versions, components, voters, watchers (nodeassociation), custom field values, worklogs, and and and Short answer - I really wouldn't do it that way. I'd click "delete" on the unwanted projects. Or,…
-
It's another product, so yes, you need to add it (and it's costs) to your account.
-
Go to the list of repositories and click the cog to the right and side of it - there's a delete option on it (assuming you are an admin)
-
Crucible is part of Fisheye, it can only run within Fisheye. The error you are getting is a simple one - your code repository does not respond when Fisheye/Crucible is trying to connect to it. Try some simple "read" actions on the command line on the server to see what they do - they'll probably fail as well, but give you…
-
No. You can have very similar names (e.g. "Project X" and "Project X.") but not identical. You can put them in different categories. Obviously, they will have to have different short-codes as well. I'd advise not even trying it though - people WILL get the project wrong when raising or looking for issues.
-
Cloud has it's own user directory system and allows for google authentication as well. That's it. It does not expose its internals and it can't be used as a directory for other systems. I suspect webhooks and connect add-ons are your only options for updating other systems.
-
I think I've seen this before, when a version contained a (security?) flaw that was spotted very shortly after release. If it's a moderately serious fault and your download logs say only a handful of people have downloaded the release, it's probably better and easier to pull the release instead of leave people with it and…
-
It was resolved, and not re-opened, so it's either gone away or not been reported again.
-
Duplicate of https://answers.atlassian.com/questions/244887/issue-with-agile-user-story-map-plugin(which has a bit more info)
-
No, it's done this way because the list of fields can change between project and issue type. Until you've chosen a project and issue type, the system has no real idea what to show you.
-
You can't "configure" this, the functionality is not there. You'll need some code, but I don't think *just* a post-function will do it because the version field requires you to select a value from a list and has no functionality for adding new versions. You'll need to think of a way to catch the data from the user (e.g.…
-
I'm terribly sorry, I completely misread this. Please ignore my previous comment.
-
You probably want to talk to Sergey's team at Plugenta about this!
-
No, Cloud is simply open to the internet, there's no options for unusual network setups. And, no, Cloud does not support SSO with external applications/sites
-
Could you share the versions of JIRA, Confluence and Calendars in use here?