Comments
-
JIRA doesn't have project level fields, the header in your screenshot is a fixed list. As well as the request Tarun mentions, there's an add-on called "Pro Fields" which implements project fields (and enables some of them to be summaries and calculations). Might be worth a try, rather than waiting or writing your own.
-
No, as I said, Cloud has it's own user management system. You manage users for Cloud in there, not in one of the Cloud applications that it backs.
-
Not one that does it the way you describe. There is another option. With the ScriptRunner add-on, you can create "Behaviours". To get close to what you want: * Create a simple select list with some of the errors you know about already * Add a last option with a name like "New error" * Create a new short text field, again…
-
It's all bundled. You may need to download a database driver in some cases, but for most installations the only thing you need is the JIRA Server download.
-
Cloud has a different user management system. See https://confluence.atlassian.com/cloud/manage-users-and-groups-744721623.html
-
The vendor of the add-on you are using for "Agile Heierarchy".
-
It's https://support.atlassian.com/contact to raise a support request, although the best route really depends on what type of system you have. If you're on Server, you might find it easer to use the "raise a support request" from within the application, as that bundles up and sends the basics of the information Atlassian…
-
You'll need to make a code change to disable the rendering function that does that.
-
Yes, you need to be a JIRA admin to do that, so one of them did it. (Project admins have some more admin rights over fields in 7.4, but only in certain circumstances, and I'm not sure the renderers are changeable even then)
-
The REST APIs for Cloud and Server are a little different in places, but it's at a detail level, where one has a function the other does not. You should find that your application works fine with Cloud.
-
That sounds like an oversight in the Agile Heierarchy add-on, it's not escaping the text properly.
-
Default Text Renderer means it uses simple unformatted text. You'll need to get that changed to a renderer that does format text.
-
That's pretty much what a Scrum board's backlog does already. To expand on that though, think of it like this: You have a workflow that starts with "new", and those issues should not go into the backlog until they've been examined and had some planning done. The next status is "to do", then "development" and so-on. To keep…
-
That's going to require an add-on for a new field type. It's also going to be quite a hard one - the baseline select list is a set of options in a llist set by the admins. You're asking for a dynamic recursive list where the option list is drawn from existing issues, and of course, the ability to add ad-hoc ones (without…
-
I tend to use ScriptRunner because I've got free access to a horde of experts in it, so I'm not that familiar with the alternatives. Check the marketplace for that, JMWE and maybe a search for "last updated"
-
The report simply needs a list of issues, so your filter can be for any issues you are interested in reporting on. But, there are a couple of things that you need to check if you are missing reports. First, check the data. The gadget only looks for the first comment added by someone other than the reporter. Second, check…
-
It's impossible to measure progress without a metric and data for that metric.
-
You'll probably need to consult the documentation or help for the application you are trying to connect to. This does not appear to have anything to do with JIRA, or any Atlassian application, so I think you are in the wrong place.
-
Looks like the field configs to me
-
You'll need a bit of code to do that. The columns are all issue fields, and you need a derived field to expose the user you are looking for. A derived field calculates something, usually from the issue data, and displays it. I'd use the ScriptRunner to create a scripted field that looks at the issue history and pulling out…
-
You don't say which capacity planning add-on you are trying to use, so I am guessing that you are trying to use one of the first two returned by a quick search on the marketplace - https://marketplace.atlassian.com/search?product=jira&query=capacity Neither of those two have a Cloud version, so you can't add them to Cloud.
-
This is one that https://support.atlassian.com will need to look into for you. We'd need logs, but only they have access to them.
-
First thing to check is the field configuration for the project and issue type. What "renderer" does it say it has for Description? If it's plain text, that is the problem, as you need the rich text one.
-
Yes, a reverse proxy with all the SSL terminated in one place does make it easier! On the user directory, I would generally not set that up during installation. Get the basics working with an admin account with the internal directory separately for each application, then pick one and add the remote directory to it. (I tend…
-
You should be able to use the documentation on using a new certificate, just skip the bit about generating the cert.
-
I'm runnning all my Atlassian applications on a single Postgres server. It's not an unusual set up. Check the "supported platforms" page for each application to make sure you get the right version of the databases. For the question of multiple servers, you need to run two services here. One Confluence, and one JIRA, with…
-
Last time I used JMWE, it was simply the user's login id.
-
Same answer - the url for Cloud is fixed
-
Create the group as normal, then go to global permissions and add that group to "bulk edit" Note that it's a flat bulk-edit permission, they will be offered, Move, Update, Transition, Delete etc (although those are then further controlled by the project level permissions - bulk edit won't let your users do things they…
-
You can't assign issues to groups, only individuals.