Comments
-
Restoration from backup is the only way. Did you take a backup before deletion? Cloud does not do backups for you here (they do it for disasters, but not individual sites).
-
No. Atlassian have it on the to-do list, and have not said they won't do it, but at the moment, you still have to migrate to a new site.
-
Some context would help?
-
There's no excuses needed - screens are the most layered and fractured administrative things in Jira. As with most things in Jira, the trick is to see that most things in Jira don't directly belong to each other. You define abstracted global things (status, screens, custom fields, workflows, etc) and then tie them to…
-
Possibly. Jira Software has three layers - Epic, Issue and sub-task. Stories are the focus of Agile, and are done at the Issue level, but actually, Jira doesn't care what you call them, or if you have different types. You could define issue types of Story, Issue, Thing, Penguin and Clock at the issue level. They're all…
-
I am afraid not, you really do have to go through each scheme to check for <anyone>
-
>I don't see a way to add the Resolution field to my screens without having it automatically set That's because you should never do it (because of the historical design and use of the field) Resolution should only be put on transition screens (never create or edit), on transitions where you want to close the issue. If you…
-
You could reverse a hash, but given the Earth's current computing power, it would be trillions of years and you'd still end up with billions of potential passwords (clashes). This is why we use hashes, rather that storing easily-cracked passwords.
-
Should be jira.permission.move.<people> It's the permission to move @Legna Garcia- Lithium (this platform) has a bad habit of sticking control characters on the end of links. Try the url again, but strip the %/ type garbage from the end of it.
-
Yes, you have changed something. By default, Jira caps exports at 1,000. That has been the same since Jira 2. If you were allowed more, you were over-riding it with the url-parameter trick. In your current Jira, your administrators have altered the cap, and put the hard-lock flag on it to stop the url-parameter trick. Most…
-
Yes. Admin -> Screens -> Create screen. You'll get one with no fields at all. You will find you can use it for create (with the caveat that Jira will still need to know project, issue type and at least a summary), edit and transitions.
-
This conversation started in 2012, when it may not have been possible. You might be able to do it now by having different workflows for each issue type, and for the ones you want to prevent "move" on, place a workflow property on every step that blocks the move permission. Not sure though, I have not tried it.
-
What do you mean by "list"?
-
The exports are capped at 1000 to prevent large downloads destroying the performance of the server or even crashing it. You can change the cap, but it is strongly recommended that you do not. The fact you are getting a "forbidden" message does in fact suggest that your administrators are aware of this problem and have put…
-
Apps have to be purchased at the tier of the number of users you have. (In the case of Jira, it's the highest tier of the three applications - if you've got 100 Core, 250 Software and 10 Agent licences, you pay for add-ons at the 250 user level, not 360)
-
Consider a move to the Server version (either hosted yourself or by a 3rd party service provider) - Server won't be getting the new interface for a while, and hopefully that time will be long enough for Atlassian to fix all the problems with it (although I can't see an easy way to fix it other than moving back to something…
-
To be clear, the password is not encrypted, it is salted and hashed. It is not stored by Jira. It is mathematically possible to get a plain text password back from a hash, but it's practically infeasible at the moment.
-
Where are you seeing "nopass"?
-
Once something has been marked as spam, reposting the same thing triggers similar test to be automatically marked again. I don't know what the anti-spam robot thought was wrong with your question though, looked fine to me. I have pulled it out of the spam folder now.
-
Upgrade to 7. You're on an old version which has known security issues, and is no longer supported, so there's no patches or fixes available for most of these. Although I would point out that 5. This is a failure of your security scans, not Jira. You want autocomplete enabled so that users can use password safes in their…
-
Cleaning the xmlcan be done by searching for the stuff that cannot be handled by your database and manually removing it. However, try the xml-cleaner first - see https://confluence.atlassian.com/jira/removing-invalid-characters-from-xml-backups-12079.html
-
Your workflow has been built to resolve issues when you move into the status that is in the verification column. If you don't want to resolve the issues when doing that, you will need to amend the workflow so that it does not ask you for a resolution (or set one for you) when you move it into that status. Talk to the…
-
Yes, they all work. Once you've got a Jira Core installed, you can add Software and/or Service Desk to it from within the application. Confluence, it sounds like you will need to install manually.
-
Groovy directive, short for "define". It creates (untyped) variables in a script.
-
You can add both "user picker" and "multi-user picker" fields to issues. As many as you would like.
-
Cloud does it by offloading it on to your directory provider effectively. Server can do it, but it needs add-ons to provide it.
-
>What I see is, their is pencil icon on the field but it still doesn't allow inline edit, but through edit screen it is writable The only way to do that that I can think of is through a customisation, like a behaviour or injected javascript. I think there are other add-ons that can block it too.
-
So whatever you are doing is not writing to the issue at all. Could you also tell us what you are doing to change the status and what the workflow looks like?
-
If you can see the issue, you can see the history of it (unless you have a heavily and badly customised Jira system). When you go to the main issue view, do you really not have a "history" tab? We need to see the history, it tells us what changed. Could you also tell us what you are doing to change the status and what the…
-
What are you doing to change the status? What does the workflow look like? What are the symptoms? (Any errors? Or does it just appear to go through the transition ok and then the status doesn't change?) What does the history say for what you have just done?