Comments
-
You're 99% of the way there. I think of permissions as having two types - system and workflow, and there's a slight grey area on some of them. It is mildly annoying that permission schemes present these as though they are the same thing, but it is for historical reasons, and arguably a better interface for admins. A system…
-
SHOUTING at us and giving us zero information is going to get you nowhere. If you cannot "do Jira setup", then all I can tell you from your question is "you are doing it wrong". Whether it's because you can't follow basic instructions, you've not read the docs and are trying to do it on inappropriate hardware, you don't…
-
Give "create issue" to everyone who needs it in the permission scheme (e.g. role: users). Use conditions to control the reset (see https://confluence.atlassian.com/adminjiraserver/advanced-workflow-configuration-938847443.html )
-
See "conditions" in https://confluence.atlassian.com/adminjiraserver/advanced-workflow-configuration-938847443.html
-
These are calculated in the chart code, not exposed in the API. Your code will need to read the basics and work them out from the data it fetches.
-
Yes, look for Project Configurator and Configuration Manager in the marketplace
-
You do NOT make it editable. You should only set it when closing an issue, and, you should *always* set it, or Jira does not work properly. It does not matter if you think you don't use it, Jira needs it to be used properly. See yesterday's discussion on the same matter at…
-
For the most part, yes. The REST APIs on Cloud and Server are mostly the same, so a JRJC based application will talk to both of them the same way. However, they are diverging products, so do not expect them to be identical, and certainly plan for them to diverge further. I suspect all the basic stuff will remain the same…
-
That has nothing to do with JRJC. Application links are for linking Atlassian applications together. The JRJC is a program that gives codes a client library for handling Jira REST calls in their applications.
-
Confluence is a wiki, not a form filling tool. Four of those six functions are not generally in the slightest bit useful in wikis, the fifth is possibly arguable and the sixth is a case of Atlassian not destroying one of its partner companies by implementing their work itself. It sounds like you need something more…
-
Sorry, I was not clear on that last one. We are not that concerned about what you are trying to get for the end user. Your problem is that you appear to be trying to run a Connect add-on on a Server. This will not work, you need the Connect framework there for it to work. Assuming you have fixed the problem with the { that…
-
Please read the previous comment again. All of it, not just the first line.
-
Ok, make the space accessible to "anonymous"
-
So it's not that it's not available, it's that you have not installed it. I don't think it will ever become part of the Confluence core.
-
Top right.
-
Assuming it's not one you wrote yourself, the list of possible culprits is at https://marketplace.atlassian.com/search?hosting=server&product=jira Take a look at the workflow though - it should have "unknown validator" listed, and at least give you the class name for it, which you can pop into google or the marketplace if…
-
It looks like your workflow uses a validator that is provided by an add-on that you have disabled or removed from your Jira.
-
So what's the point of your question? It's already available online. You can make whatever pages you need now.
-
If you don't map a status, then issues in it won't appear on the board. The backlog IS the board. So if you've chosen not to see it, you won't.
-
I would do this by the criteria. For each of your criteria, I'd have a common "type" of space (ideally, blueprinted) with all the relevant predefined templates in them automatically. The Product spaces would obviously be product focussed, and the OU probably more team like. I'd suggest a look at "Confluence Questions" for…
-
It's a customised Lithium installation. There's loads more info there.
-
Generally, you'd assume people sending emails to raise Service Desk requests are customers. Customers are free accounts (with access only to portals and their own requests). If they're raising Jira issues (Which are objects that sit behind requests that agents and participants have more access to), then they'd need a Jira…
-
You will need to expose your Confluence server to the internet, either directly or on a proxy. It will need to be put on there behind an IP address you own and control, and you'll probably want DNS for it. Once you have your Confluence online, then yes, you'll be able to do Confluence Wiki thinks with it, as you suggest.
-
I can imagine doing it with Jira, but you'll need add-ons to get close to your list of requirements, and even then, some of it won't be close. A lot of it can be done with plain Jira and Insight, the asset tracking add-on that could do all the CRM and item types. The stumbling block is the shopping type thing. You could…
-
https://jira.atlassian.com/browse/JSWSERVER-7203 - was closed years ago, but actually, re-opened a couple of weeks back to gather more interest. Worth hitting vote on it.
-
You can't move a sub-task type, it belongs with the parent. So you'd have to create the bugs at the same level as story. That will work, because if you don't complete them in this sprint, they will move to the next. But it does give you the problem that you are now reporting that you are delivering stuff with known bugs.
-
I'm not quite sure what you are trying to achieve. Confluence is already a "wiki" and the posting over at medium is pretty much using it off-the-shelf. I would recommend creating templates to help your users structure their input along standardised lines, and show them clever stuff like linking, macros and page properties,…
-
Ok, I need to be careful here because of "Jira Speak". Jira has a very specific meaning for the word "component". To clarify, do you mean * Jira's Component field * A custom field you have added and called "component" (I'd suggest you pick a slightly different name to avoid confusion) If it's the Jira component field, then…
-
From the installation. The licence is not locked to a version - a server or data-centre licence is valid for all versions released before the end of the licence. (Well, ok, if you go back far enough, like to Jira 3, you have to get different format of key, but it's still a valid licence). The licences you've got there…
-
What are the errors you are getting?