Comments
-
There's nothing resembling most concepts of "sub-projects" in Jira. It doesn't make a lot of sense in the context of Jira. The standard answer when someone mentions "sub-projects" is "use the components field to break up your project into sections"
-
Yes, it's an easy thing to do, but you need to be able to define different periods for different users. The recommended default for scrum is indeed 2 weeks. Kanban doesn't need the periods and hence doesn't record the period.
-
Please also see the other guidelines at https://community.atlassian.com/t5/Marketplace-Apps-articles/Atlassian-Community-guidelines-for-Marketplace-vendors-and/ba-p/689723
-
Indeed, the sprints are not separate, they're the same object. So you will see the new name everywhere the sprint is shown.
-
You're not supposed to be adding Story Points to sub-tasks, as it doesn't work and hence Jira doesn't support it.
-
https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html is the starting point for changing the database
-
It's also an exception to the way all the other fields behave, which adds more confusion! Although it's a "basic" part of the way Jira works, I wouldn't say it's obvious or intuitive. I don't think I know of an admin who has got this first time they've run into it, we've all either had someone explain it to us, or worked…
-
What do you mean by "tied"? At a guess, you mean "user who has some level of access to the project", which is not a simple lookup. Instead of looking for a technical answer that might not really be useful for what you're trying to do, could you explain why you ask? What are you trying to achieve? What is the question…
-
You are confusing the mandatory flags with the way the field has been coded to work when placed on a screen. The resolution field already is optional and cannot be made mandatory in the usual Jira meaning of "mandatory". The answer to what you're trying to do has already been covered on your previous question on the same…
-
You can upgrade to any version released before the end of your licence time. As you've got until Feb 2019, yes, all current versions are available to you.
-
It's not JQL, it's a shortcut for admin. Mizan said "Type g g", not "put it in a query"
-
Ollie's description is correct, you cannot have partial admins. You could do it by removing all roles from permissions, notifications and so-on, using only groups to grant access. This will, of course, leave your administrators in group-maintenance hell, but that is effectively your goal.
-
What are you trying to map with this?
-
It's not technically mandatory, but it gets a value selected when placed on an edit screen. What you need to do is remove the field from the "create" issue screen (and "edit" if you have it there) The resolution should only ever be put on "transition" screens in transitions going from "open" type status to "closed" type…
-
Set up the project notification scheme to send email back to the reporter when "issue created".
-
I've used the Riada Insight add-on that does asset management and can have an automatic network asset scan function added, but I don't know how that compares with those things.
-
I agree that it's not intuitive, but it's not about people being incompetent, just that they're struggling with what is simple in theory, but almost always appears complex because it's generally set up in a counter-intuitive way (and that includes a new off-the-shelf system - the defaults themselves are a pain). I have…
-
When you move from Cloud to Server, the user IDs become disconnected from the Cloud user directory. The export/import process is aware of this, and creates a system admin account for you to use to get into your server install and reconfigure it all. Log in as sysadmin with a password of sysadmin too.
-
You should target either 7.6 (it's the enterprise release, so will have long term support) or 7.10 if you want the "most stable" and plan to upgrade more regularly (as it won't be patched, just new releases done) The features and benefits are listed in the release notes for each version - see…
-
The instructions are complex because there's no other way. There are no "trash" add-ons either, as it's simply not supported. This is why the standard recommendation is "never allow delete for most users". Give them a resolution like "deleted" or "raised in error" so they can close issues they don't want with a good reason…
-
Bugs should go to https://support.atlassian.com/contact first, especially for Cloud, as a support request. Atlassian will convert it to a bug if it is one. The community can try to help you, but a "bug" here is pointless.
-
<sigh> No, they're not numbers, as I've already pointed out.
-
This is the same as what you asked the other day over at https://community.atlassian.com/t5/Jira-questions/Problem-with-resolution-and-status/qaq-p/813822
-
@miikhy turns out the cat has now forgiven us, judging by the tuna-scented hiccups! I bribed her for forgiveness @Matt Doar Center not Centre. Yes, very true. But as an English person who went to an English grammar school, my paws betray me when typing centre. I know it's center in American English, and that is what the…
-
Nope, no good, still mis-hearing this as a reason to dance badly. Or bad[ger]ly... http://weebls-stuff.com/toons/badgers/
-
To try to run through the original questions instead of getting side-tracked on comments: * Have you noticed improvement in differentiating this content after we introduced the new cloud/server tagging in the create flow?* Heck yes. In the last 3-ish weeks, I've only asked "Server or Cloud" a couple of times, and my "Oh…
-
Atlassian do have a poor record of choosing group names - Cloud, Server and Data Centre all confuse users (OnDemand was clunky, but unmistakeable). "App" is utterly dreadful, as most of the world sees it as a contraction of "application" which has another meaning in the ecosystem. But, we're at the whim of the marketing…
-
Sorry, I've not looked at the code side of Kintana before, but if you need code repositories, Bitbucket, and if it's the CI/CD part, then Bamboo.
-
Jira at the core, with a good look at Portfolio, Software and you will probably find Confluence extremely useful too. But definitely Jira at the heart of it.
-
A Jira query finds issues, not projects, so it's probably already giving you the right answer. I'd summarise probably. Save your filter, create a dashboard, and add a "filter statistics" gadget to it. Select your filter and the "field" called Project. You'll get a bar chart listing the number of issues in each project.