Comments
-
Not really. Once a username has been created, it's the unique key to that user. They can change their name and email from their profile, but the login id is immutable. It's used all over the place, which is why changing it can be a pain (imagine having to rewrite every table where a user may have left a footprint - last…
-
Not really. Once a username has been created, it's the unique key to that user. They can change their name and email from their profile, but the login id is immutable. It's used all over the place, which is why changing it can be a pain (imagine having to rewrite every table where a user may have left a footprint - last…
-
The audit log (if enabled) can be filtered for delete, but otherwise, no. You can't report on what's not there. The closest you could get is look at the while list of issues in the project, and look for holes in the numbering - a hole is either a deleted issue or one that was moved out of the project.
-
It is, if you enable the logging. Better, disallow delete, it's easier.
-
I'd raise this, as soon as possible, with support directly - Michael may well see it here, but they'll need an official support request in order to do anything. Head to https://support.atlassian.com and have your account details to hand (contacts on your side, and at least the url for your Cloud instance)
-
Please see the original answer. You or someone or an automated system, using your credentials, deleted the issue. You can't get it back or find out who/what unless you have got logging enabled to catch this sort of thing.
-
No. Deleted means deleted, the only things left are a hole in your project key numbers and (hopefully) a backup. I know OnDemand is backed up, but I don't know if Atlassian will retrieve it for you, and if they do, whether it'll be a simple copy of the data they found, or a full re-insertion of it all (Which needs SQL,…
-
Because it really is totally variable. Look at an issue. It is possible to set up an issue that is as small as a single line in a tiny handful of tables. If it's just got a summary field and nothing else, then only jiraissue and a couple of workflow tables make up the whole thing. Then a line in the history to say "it's…
-
Sorry, I was hoping you'd tell us a bit more about what you're doing. If you're using the SDK, there's no "sign up", but if you're using a proper development licence, the whole story changes. Although neither will affect your admin password, but I don't know where you're using it!
-
What development licence are you signing up for?
-
No, I'm afraid email is either on or off globally. You could simply delete all your notification schemes from test though - that would cut down emails to just system notifications (i.e. user create) and subscriptions (I think there's a way to turn them off too, but I'm not sure)
-
Please be aware that boards are not "under a project", and that's why this works. A board exists. It selects issues and allows you to work with them. Often, it will be selecting "project = xyz", but they can select from many projects, or take parts of projects rather than the whole. If you delete a board, it doesn't touch…
-
Yes, that's what we've done with Script Runner - injected a web-fragment that runs a script which creates a copy of the service request in the dev project and links them. A variation I've done in the past was to build it into the service request workflow, so that the agent would simply go "passed to dev" and that would do…
-
Without any scripting or automation, the best I can think of is "clone" - clone the issue that the service request created, then move that instead. You'll at least have a copy of the data and the link back to the original.
-
That's true, you have to look in the history of the issue, and be aware that the old issue id it had refers to a service desk project. I don't think Atlassian really expects you to move issues like that, especially as doing it will remove a customer's access to the issue they raised (not that there's any particular support…
-
Yes, you can link issues from one project to another, even if the projects are handled by different applications.
-
In order to know what access someone should have, Confluence needs to know who they are. So they need an account to log into. Unless you enable "anonymous" (never for any access other than read, of course, or you can't track the activity). What you need is the ability to authenticate people, but not identify them. So that…
-
If it's working for you, you might want to stick with it. I'd be tempted to ask Atlassian what's going on though, if you're sure you (or rather, one of your other admins) didn't set it up!
-
Actually, Jira-users is one of the three standard off-the-shelf groups for Jira. So, I'd normally be tempted to tell you that you've removed Jira users in the past, and someone has added it back in. But, Atlassian is currently working on the user management side of things, so you may have been affected by their changes.…
-
I'm not sure what you're asking for here, the diagram looks fine for me. The green line shows you resolving issues - 28 The red line shows incoming new issues - 21 The number of issues in your project is not important in this chart - if you have 37 now, then because your chart shows 21 being created, then you can work out…
-
I think that's the closest you are going to get - it's there to support multiple value selections in a single field. Anything more complex (like your requirement) could use it as a starting point, but you've got a lot of complexity there that simply isn't in Jira.
-
Ah, that's better. No, Jira doesn't have anything like this, and it's quite a complex requirement. You CAN of course, write something to do it, but I'm not aware of any plugins that come anywhere close to that.
-
That looks like a standard multi-select field to me. Could you explain further? Why won't a multi-select field do the job?
-
Not really any way other than a) looking at it and b) testing Maybe if you posted the text here, we could explain what it's doing and see if you've missed or misunderstood something?
-
What "script post function"? How are you doing this in OnDemand? The scripting plugins I've used are not available on OnDemand.
-
1. How are you running this script? 2. How are you doing it on OnDemand?
-
You can't, unless OnDemand has changed recently - it's an advanced change, which isn't allowed on OnDemand.
-
Your licence agreement explicitly stops you from removing the "Powered by xxx" and the link. You can move it around, format it differently and remove/reword a lot of the footer, but you *must* retain that one part of it, visible, readable and clickable. I don't know if Atlassian may allow you to remove it for certain cases…
-
It's not needed on most transitions, and most users tend to be good at reassigning stuff. Most places have a clear "the assignee is currently responsible for this", so when a user is looking at an un-closed issue that they are assigned to, the instinct is to get rid of it, and there are basically two ways to do that - deal…
-
They're almost in the same tab ;-)