Comments
-
No problem. It's one of the least intuitive or obvious things in Jira! It bites almost everyone sooner or later.
-
Only administrators can create and do the structural administration on Company Managed projects (that's the whole point of them being company managed - the users don't look after them, the admins do)
-
There are no "workspaces" in Jira, it's a pile of projects. >My client want to hide the Closed or Cancelled projects That's fine, but it's up to your administrators to use archiving or hiding a project when a project is closed or cancelled, not the client. You absolutely should not be doing it at an issue level, which is…
-
I am a little bit lost on this question. Requests do not have child requests. Do you mean issues (the issue behind a request) and their sub-tasks? If so, then yes, you should look at whatever you have coded that copies the data down to the sub-tasks and add logging to that.
-
Crowd is a user directory/management system, it has nothing to do with the issues. Same with Access - it's not going to report on issue history.
-
Welcome to the Atlassian Community! There's a couple of things that might be happening here, but I think we need to start with an explanation of where the strikethrough is coming from. A struck-out issue is resolved. Jira is looking at data that you've put on the issue to tell it the issue needs no more attention. This is…
-
Welcome to the Atlassian Community! What do you mean by "not supported"?
-
You will need to talk to your administrators.
-
The usual reason for this is that your issues were not completed at the end of the sprint - they were not in the "done" column when you closed the sprint. A complete issue is flagged as complete by being in the last column (whatever you may have named that). Its actual status or resolution is irrelevant, all that matters…
-
Welcome to the Atlassian Community! The UWC kind of fell out of use, and then support, as so many people had already migrated their legacy systems off stuff like Trac, that there was very little need for it any more. I've had some success with it all in the past though (one project very recently) - firing up an old copy of…
-
This is more of a human problem than one you should be trying to fix with tech. Blocking people from doing this is not the right approach, the right thing to do is get them to do their job properly. You don't really want to stop people bringing new stuff into an active sprint. You want to have them finish what is in the…
-
Hmm. Ok, you'll have to do it manually - take the filter, and add "and not project in ( )"
-
You do not. A REST call has nothing to do with the UI, there's nowhere for it to trigger a screen. Your code will need to implement a UI to pop something to ask the user for the data that Jira would ask for in the target transition screen, and feed the data to the REST call that is attempting the transition.
-
The error message is pretty clear - their accounts do not have "add attachments" in Confluence.
-
This appears to have nothing to do with Confluence. Especially as you should never be looking at an Atlassian database, let alone running DDLs against it. I suggest you ask in a forum related to whatever system you are using.
-
Welcome to the Atlassian Community! There's no way to do it - a copy of a file is independent of the original, so if it's changed in some way (including being renamed), there's no way to know what or where the original was unless the copier attributes it.
-
I would point out that a lot of those are probably being called by apps, not the core Atlassian systems.
-
Click on the sub-slice, it will give you a filter for the smallest pieces included in it. You can then report on that.
-
You will also struggle to do it with advanced tools for automation and scripting. Moving an issue to a new project or type is something that should only be done as part of housekeeping or correcting the odd genuine mistake. It should never be a part of a standard operating process, and certainly should never be automated.…
-
Ignore the field configuration for a minute. Go to the field configuration scheme list - do you have "delete" on any of the schemes? Most importantly, does the one "for project TES" (not TEST, TES, as in your screenshot) have an option to delete? If so, delete it, and then go back to try to delete the field configuration…
-
Welcome to the Atlassian Community! Your best bet is probably to talk to an Atlassian partner about getting some training or just advice in general.
-
You didn't ask for that before, you asked if there was a history trail (an audit) Yes, there are historical reports, but you probably want to look at apps that can provide raw dumps of the history (they're not actually that useful though, the best thing to do for an "audit" is look at the system)
-
Ok, so you'll need to stop using GCM. It's obviously causing you problems.
-
It is possible to set up fake Atlassian accounts and use them to create maliciousl systems which can then send emails like the one you got. If in doubt, forward the email to https://www.atlassian.com/trust/report-abuse (no need to write anything for them, just forward it in full). Then ignore it.
-
You'll need to grant the user whatever roles, groups, or other settings that are used to give them permission to transition issues in all the "different" projects.
-
I would question who is telling you this, and how they think it might compromise security. (It could, but in only very specific and limited scenarios)
-
What do you think "compatible" means? You can connect Bitbucket to any version of Jira from 4.0 and above with an application link to Confluence 3+, Bibucket 2+, and and and... This will enable some data exchange between the two linked systems. Exactly how much you get does depend - a Bitbucket 7 might not get as much of…
-
I wasn't asking about the setup of your Jira, I was asking why you've set up your systems in such a complicated way that makes you want to make it harder to track issues in your issue tracker.
-
No problem - it's one of these problems where if you misunderstand one tiny little part of it, the whole thing looks like it needs framing differently. I'm not saying you've missed anything about your process, nor that you have misunderstood what it does, but that there was a small flaw in how you meld them together. Which…
-
Welcome to the Atlassian Community! To make a question accessible to the wider audience, and hence more likely to get an answer, it is worth writing it in plain language, avoiding jargon and obscure acronyms. Where are you struggling with your Flash Card Reader, Fast Ceramic Reactor, or Free Credit Report, and what has it…