Nic Brough -Adaptavist- Expert

The project is not being deleted. You are applying a permission scheme to it that does not include you as a person who is allowed to see it, so it is being hidden from you. There's an important security concept here that a lot of software implements really poorly, and I think you're assuming Jira gets it wrong too. It does…

Yes, I know, and that's one of the reasons I never use gmail's web interface, it doesn't warn me it's going to do something bad and, well, it does something bad without me asking it to.

Ah, @Rob Horan has just reminded me of the lolly I really want: https://www.facebook.com/watch/?v=1070310753103610

With a caveat that I really don't have a sweet tooth and only really got them when the grandparents, or, later, the nieces or nephews were insisting and I didn't want to be the odd one out... The Lego-head voice in my brain is yelling "SPACESHIP": https://www.instagram.com/p/BVmi_nIhAYO/ But I remember being equally fond…

I'd be curious to hear the use-case too, Confluence is a very different wee beastie to Jira.

Ok, that site exists, so somebody has set it up, but if it's not appearing on your list of sites when you go to admin.atlassian.com, then you're not the site owner or an admin, and it must belong to a different account. If you've lost the account with which it was set up, then you'll need identify that account and reset…

Ok, great, thank you! So it's the search. My Open Issues runs JQL that you can replicate with "assignee = currentUser() and resolution is empty" Can you try that, again as the user that is not seeing it, and see if your missing issue is in the results (I do not think it will be). Then go to view the issue directly, and…

Ok, we need to try a simple test - go into both source and target projects (in different tabs or windows) and create a new issue in there. Does the description field show the same in both (not necessarily in the same field order, but the field name, description and editor box)? If you create the issue and put the same…

Let's narrow this down a bit. Is your client looking at the request (in the helpdesk portal) or at the issue (in a Jira project or on a board)?

You don't need to duplicate it all redundently to do that. A simple REST call can look at an issue, and a second one add your classification to it after your expert system has had a look.

You've also got the problem that if you are going to do it, you absolutely must display the fact you are going to do it under or next to the link (not just in a tooltip), which means even more text on what most people already think is a cluttered screen.

This can happen when you've been creating projects that are independent of each other, not sharing workflows, but that will create multiple status, and you say you haven't got duplicates. I'd still want to check that (and you'll be doing the next debug step in the same place anyway) - go to Admin -> Issues -> Status and…

Ok, so is there a (single) Jira account associated with that email address? What happens when you log in as that user and try to create an issue in the target project?

>Group 6 represents the problem perfectly: it's an extra step. The words "perfectly happy" are actually a meaningful synonym for "patiently tolerate." No, it is not. Group 6 are not "tolerating" anything. They're happy with how it works now. If you changed it, group 6 would merge in with group 4. Group 6 is not the same as…

* Scripting with an app, or an app built to do it (assuming you don't want to destroy your data one line at a time, manually) * Scripting with an app, or an app built to do it * Space tools -> Content tools -> Export space, then Admin -> Import on the target * Export it with the export options, or include it in a space…

You could search for the issues, then use the "bulk edit" option in the tools menu to re-assign them en-masse. But generally, I wouldn't bother. If the issues are closed and the users deactivated, there's no benefits to be had by changing the issues. (If they're open, you should be re-assigning them so that an active user…

Jira does not have any theming functions itself. There are some apps that can mess with the display enough to do theming, but these are server only. There are a couple for Cloud on the marketplace, but they are based on browser extensions. If you're happy to do it that way, you might be better off looking to the browser's…

You can't. The "can see users" is either on or off for a person, there's no filtering.

Ok, but why are you not doing this "classification" in Jira? A simple label or dedicated custom field will allow you to classify and report on classified issues in Jira without having to do all the coding and processing to build and maintain redundant (and obsolete) duplicate data sets.

Ok, so that confirms "members" means "users". Now could you tell us what you mean by "link for each user added .... using filter"? What link? What "user added" and what has it got to do with a filter?

You can't do this directly, no-one has written a JQL clause for "user in groups that a named user is in", probably because it's mostly useless. The closest you can get is what Fazila said - use the "membersOf" to define which groups you are interested in. The reason a search for other user groups is useless is that 99.9%…

Move the issue into the last column on the board, and Jira will see it as "done" and drop it from the backlog. It won't disappear from the sprint, but when you close the sprint, it will be considered completely done and won't bother you again, unless you deliberately ask to see finished issues.

I'm not aware of an app that will do that directly. As a good consultant though, I have to ask why? Why are you duplicating data into another system?

You're missing the other types of user: 4. People who actively don't want this feature 5. People who don't care about it 6. People who are perfectly happy to right-click -> open in new tab/window when they actively choose to do so If you want to look at some numbers, you'll find that there are more type 5 users than the…

No, you need an app to do this, but the automation that John is describing is included in Cloud so you don't need to go find an app or enable anything.

Jira has no code to delete a dashboard "automatically". If a dashboard disappears, then either the permission for you to see it has been removed, or it has been deleted. In both cases, a human has to do that (although it could be scripted, by one of your administrators) Ask the owners of the board and your admins where it…

The example of how to do this is at https://developer.atlassian.com/server/jira/platform/jira-rest-api-example-create-issue-7897248/

This script is not quite what you need, but it does show you broadly how you might do this - https://library.adaptavist.com/entity/automate-epic-custom-field-sum (Frankly, I prefer your approach - adding sub-task estimates up on to a parent issue is almost always a bad thing to do, people tend to fail to think through why…

Status is not a field, it is a display of where an issue is in its workflow. If you want to change the status, your workflow needs to have a transtion from the current status to the new status (think of a simple flowchart - each box is a status, and the transitions are the arrows between them. No arrow from the current…

Go to https://admin.atlassian.com to maintain your Cloud systems, or log into the (Core) system and go to admin -> manage applications to add Service desk to it. However, I don't know quite what you mean by "I have registered luceed.atlassian.com" - that's not a valid url for an Atlassian Cloud site, and atlassian own the…