Nic Brough -Adaptavist- Expert

Not a direct one. You will have to replicate broadly what an admin would have to do in the UI: * read the project list and work out what workflow scheme each one is using and what issue type scheme it has. * cross-reference which workflows are being attached to each issue type in the issue type scheme (just because a…

Permissions can't conflict, they are simple additive functions. If you grant someone "edit", then they can edit things. If you grant them comment, then they can comment. There's nothing there to conflict. In confluence, you can't grant permissions to people without granting them view, so you can't run into problems like "I…

Their personal space will be put in the bin, but nothing else will be touched. Their created and edited pages, and comments, will show as being made by an unknown user, but nothing will be deleted. We usually recommend that you don't delete users, so their content remains attributable to them, but just remove them from the…

The user will remain displayed until you re-assign the issue to someone else. The list of people in the assignee list is determined by the permission scheme for the project - there is a permission for "assignable user" that people have to match the rule for to appear in the list.

Welcome to the Atlassian Community! The dropdown is listing the types available in the project. To add Story, you will need to add the Story issue type to the project's issue type scheme so the project can use it. To remove initiative, remove it from the project's sscheme.

I have edited this to remove the login details you have just provided to the whole world. I strongly recommend that you move anything you need off this account and shut it down as soon as possible, because it will have been compromised by a bot by now. You should NEVER give your passwords out in a public forum. Anyway, on…

Delete means delete. You can't get any details of the work logs you have deleted because there is no data in the database anymore - it's gone.

Edit the workflow and associate the existing status with the step you want to use it for.

No, there's no way to do this. Download and view are actually the same thing - the server gives a file to your browser to either display or save. So there's no point in blocking downloads while allowing view.

As Trudy says, there's no direct way to do this because boards are not containers of issues. The closest you can get would be to run a search for "status = done and sprint is empty". That will find issues that have been completed outside a sprint, but it can't catch issues that have been in a sprint, not completed in the…

You will need your automation to run on any change to the estimate field on every issue or sub-task. I would not bother doing this though. If you're using the time-tracking for the estimates, then Jira already does this for you - look at the time tracking panel on the issue and you'll see it includes the estimates on the…

Welcome to the Atlassian Community! Why are you trying to do this by scraping pages when the REST API can do it all for you?

I'm not aware of any app that can do that. It would probably be better to do it from the outside - when you realise you want to attach a file from your sftp server, have a process that can attach it to the issue by sending it over the REST API to Jira.

Yes, that's a way to do it, but please could you explain how Atlassian Access is set up with your Okta?

@Phill Fox - I promise I will not mention that in any of our internal meetings (unless someone hands us a good line that embarrasses you or might get a good laugh)

Even with huge Jira instances, the probability that someone will write an email that includes an issue ID that really means something else is tiny. I have worked with a place that did have a problem with it, but most of it was being caused by a couple of their departments using a legacy system that kludged things into…

You should not be trying to do this. There is no good reason to destroy the tracking information about when an issue was created. If you are repeatedly re-opening the same issue, then you should be looking at the "date re-opened", not the issue create date. Your best option, one that retains the accurate history of the…

No, it makes no sense at all. If someone replies to an email about a subject, does it make sense to go off and create a completely separate topic or thread, making it nothing to do with the original conversation? And making it look like no-one is responding to the original issue? I'll save you some time - the answer is…

As mentioned above, we need to know how you have set up Atlassian Access to work with Okta.

That makes sense, but I think you have to stop thinking in "traditional" user access terms. The dying model is "people have a unique identifier for this system, with a password, and it is only used here". The world has moved to "have an account which then gets access to <many places>" This makes "dummy users" a lot more…

Welcome to the Atlassian Community! We can't really help you with this. Your Bamboo server or agent can't download from that site, which suggests a network error, but that could range from your Bamboo's server networking settings being wrong though to the provider of the download not serving any more. You will need to go…

Welcome to the Atlassian Community! You can only have one hierarchy - the main point of the hierarchy is to structure things across your platform in the same way, so that people see and work with the same thiings. The hierarchy you describe (assuming I've understood it, which is not that likely) is fundamentally broken…

Noether of those are Cloud. If you visit either of them, you'll find there is a "help" icon towards the top right, and that leads to a list of options that contains an "about Confluence" which will give you a version number. Cloud systems won't give you a version (it's functionally useless to you) if you hit the "about"…

Welcome to the Atlassian Community! Your screenshots seem to show a running Jira, but your error message is about Jenkins. This suggests your Jira is running on a different port, and Jenkins is running on 8080.

Eh? It makes perfect sense. The vast majority of emails that contain an issue key will be replies to conversations started by the issue and a few will be from a human who wants to talk about it, and someone copies in the Jira email address so the conversation can be captured there. It would be incomprehensible to me why…

Welcome to the Atlassian Community! The bulk-edit permission is a global one - you need to be a member of one of the groups named to have it. Your admins can tell you what the groups are (and add new ones) by going to Admin -> System -> Global permissions

There's no easy way to work this out because the keys that belong to other accounts should not be shared. If you shared the key with someone, you should know who. If you were given the key by someone, then you'll need to ask them. If you have no luck chasing it down, you can raise a support request with Atlassian, and they…

The question wasn't about risks of deleting all temporary files, it was about some very specific types, and my answer stands.

Welcome to the Atlassian Community! Not unless you're willing to write an app that can extract the information from your remote directory (bearing in mind you're asking it to record data about people who may not be Jira users) and apply it to the audit logs (while avoiding compromising GDPR/privacy problems)

Welcome to the Atlassian Community! What do you mean by "annex"?