Comments
-
You don't do it in the database - Jira needs full access to the whole of its datastore in order to work. But Jira does enable you to restrict projects and even issues in many ways. Have a look at the permission schemes, and issue security schemes as a starting point.
-
Or, possibly, that the browser is broken and rendering things incorrecly. Same diagnostics though! (and try another browser)
-
No, I meant significant change to the workflow scheme, not the workflow. The workflow is the process flow. The workflow scheme tells a project what workflow to use for each issue type within it. You can't associate a workflow with a project or issue type directly, you have to do it with a scheme.
-
To save you reading the link, the answer boils down to "don't". It involves hacking the database and destroying your audit information, which really doesn't sound good to any compliance or regulator type people.
-
This is a place for the community to share, not really the place for feature requests, as Atlassian don't use it for that. Feature requests here, while it's good to talk about them, won't go anywhere. Probably worth trying https://support.atlassian.com/contact, as things raised there do make it into the Atlassian backlogs.
-
I met in the middle - I don't want to do it manually, but regular task add-ons are overkill when I only need a handful. I wrote a script which creates tasks over REST, then stuck it in a cron job on one of the Linux servers I look after.
-
That is not a problem, buy a licence for the users you need and go ahead. Do you have a specific question about doing this?
-
Workflow is not relevant here, you need permissions. See https://confluence.atlassian.com/jirakb/limit-restrict-user-s-project-access-280069544.html
-
Duplicate of https://community.atlassian.com/t5/Questions/Concurrent-users/qaq-p/646924 (Although, if you did mean Confluence, simple answer is "same as Jira, in the other question)
-
Jira is licenced on the number of user accounts who might be using it. There is a 25 user tier, so you'll be able to use a full 25 accounts. Jira comes in three versions: * Cloud - Atlassian host it * Server - you host it on your kit (or get a 3rd party to) * Data Centre - hosted like Server, but for heavyweight installs…
-
Do you need to stop the users editing the field completely, or just the inline edit?
-
It sounds like you have made significant changes to the workflow scheme, probably inadvertently. Go back to the project and look at the "workflow scheme", just get its name for now. Now go to Admin -> issues -> workflow schemes, find it and make a copy. Go into the copy and find where your old workflow is used. Replace it…
-
In both applications, go to Admin -> indexing. You'll find the options there - a "complete" rebuild will do everything in full
-
It's not a matter of it being null, we need to know what it *might* select. Could you give us the JQL of the missing board please? Feel free to obscure project names if you've got "project in (aaa, bbb, ccc)", I doubt that is the problem.
-
Great, and what is in the "import" folder? More importantly, what user is running Jira?
-
That's expected - the directory you are looking at there is the installation directory, not the home directory. What is under /Users/gopishankarharidas/Desktop/JiraHome ?
-
Do you need to stop the users editing the field completely, or just the inline edit?
-
Ok, that is going to be complex. Are the old and new servers running the same version of Jira?
-
Ok, so who is the Jira process running as? And what do you find in that directory after installation?
-
Your workflow sounds like it doesn't have a transition out of "done" - you could add one and re-open and then re-close, or even add one which loops back to done and sets the resolution A riskier option - wait until the users are offline, then add the resolution to the "edit" screen, use bulk edit to set it, then remove the…
-
What does the log file say the problem is?
-
Very good point (I may be biased because it directly supports what I was saying and the others here REALLY failed miserably to understand)
-
The options at the top are not part of a space, they are global, and hence need to represent what a user can do anywhere. If your space is correctly permissioned for (let's say) anonymous read-only, that's fine, the "create" option will still only let anonymous create in other spaces. Although there are some cases for…
-
Have you tried a search for "Fehler*"?
-
Sorry, misread it. Didn't realise it was closed, but I've changed my answer and made sure it's open again.
-
Ok, great. Most of the options will go away if a user does not have permission to use them. If you make sure "anonymous" only has access to read some of your spaces, they won't get the "create" option for example. They will still have the navigation elements. The space list will be there, as will search, but if they're…
-
You need to give us a bit more than that. What "buttons" and why? I mean, are you re-skinning it to "simplify" it for users (i.e. make it harder for them to find things), or are you trying to downgrade it by removing functions for users?
-
Ok, great, thank you. You've got some content that uses a macro that is not valid on your system. You'll need to establish where the "display" macro was coming from and fix it (or remove the usage from your pages). This can happen when you've imported from another Confluence, upgraded or been fiddling with macro settings,…
-
This might sound a little odd, but could you check the template as you create the project and read the list of issue types it is going to try to use? Compare the list with your list of issue types in admin -> issue types in plain Jira and look for the same issue types, and check that their names match in terms of case?…
-
Is this purely on the Service Desk front-end (portal)? Or are you searching in Jira?