Comments
-
I'm afraid it's not possible, yet. Atlassian are saying they're going to overhaul how schemes work soon, with a view to making them more coherent and easier to manage (actually, they'll vanish, as far as most users are concerned)
-
Work out how many users you need for each site, and hence what tier of licence you need for each (you're going to need a set of licences - one for each site). Then talk to Atlassian sales about how to reallocate the money from the current licence to put towards the new smaller separate licences you need to get.
-
I'm afraid JIRA doesn't record the source of an issue explicitly. The closest you can get without coding is to have a field on the create screen that is optional and defaults to a value, then you'll know that when it is filled in, a human did it, rather than an email. (Although this won't stop the human blanking it out,…
-
The extended mail handler (JEMH) will do it too. The reason you can't in off-the-shelf Jira is that emailing people without "browse" permission is a bad thing to do. Until you've thought about it carefully and actively made the decision to do it. Hence the default position of not allowing it.
-
You don't. Issues do not belong to boards. There's no such thing as "copying from one board to another". You have boards which select a range of issues to show you depending on their filter. My best guess here is that you are not choosing to clear the sprint when you clone the issues.
-
There is a relationship somewhere, the issues must be in the sprint they're blocking somehow. There isn't a way I know of to get an issue out of a sprint while it remains in it like this.
-
Issues do not "belong" to a board, they are selected for inclusion by a board, and can end up on many boards. Anyway, do the incomplete issues have any relationships with the issues in the sprint being closed? An obvious one is if you include them in shared Epics?
-
Sprints belong to boards not projects. If you need people to run different sprints, you need to define those sprints separately on different boards.
-
Click "create". Either on the parent page, or just move them to the right level when you've created them.
-
You don't need any workarounds any more - Atlassian fixed it a couple of years back.
-
Yes, that's correct behaviour, given that Jira doesn't log creator correctly. I prefer solution 1 as it's perfectly clear
-
Not really. When you create an issue, Jira creates it with whatever reporter the user enters. That's it, the first time the issue exists as an entity, it has the reporter on it. If the user changed it from themselves to someone else, you're a bit stuck, because the person doing the typing doesn't actually commit that into…
-
Ok, so when you log into Jira as that user and look at an issue? Do they see the "due" field? A couple of other minor points - I'm sort of assuming by "due", you mean "the due date", the system field? Also, you aren't using any plugins like behaviours, field security or something else that obscures fields, and you haven't…
-
The message you are getting is telling you what is wrong. The filter you are choosing has errors that you need to fix, specifically that the project you've selected in the filter does not exist and that the field "due" is not included. In both cases, it could be because the current user cannot "browse" the project, and…
-
It really depends on the nature of the change you've made, but it's quite a complex set of things that you can do that *might* require a re-index. The system message you get when you change fields is over-cautious and asks you to re-index when you don't need to quite often, but it's quite hard to know when it's actually…
-
Go to the notification scheme and add a new notification, selecting "custom field" and then the name of your user picker field from the list.
-
Ok, what's the error message(s)? Have you checked permissions?
-
The ones I've done with the script runner are site specific and hence probably useless to other people. It's far better for you to do it, so you get the rules you need correct and learn the script runner for yourself.
-
You'll need some code. Although I'd advise looking at plugins first. There is a risk-management plugin which lets you do some similar things, and has some helpful reports and displays. If that's not suitable, then I'd look at the script runner plugin, because that can create "scripted fields" in which you can embed your…
-
There is no question here, just a set of data. What are you actually asking us?
-
Bother, sorry, have a look for "project creator" and "project copy" in the marketplace: https://marketplace.atlassian.com/
-
Your requirement is for a new project type. You can only do those with code (add-ons are code written by someone)Have a look for project creator and project copy in the For custom fields that will be added to new projects, you need to use a project type that uses the global default schemes, and create custom fields with a…
-
You will need to write an addon to provide a new "project type" (see https://developer.atlassian.com/jiradev/jira-platform/projects/tutorial-creating-a-project-template ) or use an addon that provides project copy type functions.
-
Admins can change the ownership of dashboards too, but not edit them. I try to avoid altering other people's dashboards and filters, they often get very upset when they find someone else messing with their settings.
-
I tend to include "project lead" in the "Can administer project" permission in the permission scheme as a default - makes sense that your Project Lead should be able to maintain components, versions and users in their project.
-
See https://confluence.atlassian.com/jirakb/jira-timesheet-reports-and-gadgets-removal-from-jira-cloud-792504481.html for the explanation of why it went, and alternatives
-
I think your testing has shown that.
-
Ah, ok, yes, you're overloading it, it's not designed for 2k issues.
-
Have you tried re-indexing? (Also, check your base url is correct, although I doubt that is a problem)
-
1) Not without code 2) No, but it's a doddle to create one