Comments
-
* Yes, the created field * If you build one into your workflow, yes * If you build it into the workflow, yes * Because you've not given it to Jira, you're not looking in the right place, or you've not configured it (I can't tell what you're looking for from "some of the information") Jira logs all changes to issues in the…
-
"i've update the username directly in Crowd." - via the UI or did you break it with SQL?
-
It sounds like you did not think through the permissions, but I didn't mention this. Go back to the permissions, and I suspect you will find that the role "users" was also used for "browse project". You are going to have to work out how to separate out "browse" and "create" - I'd change the scheme so that you have…
-
Ouch. That means the database has been damaged, probably corrupted beyond use. There's a good reason the system tells you the h2 and hsql databases are not suitable for production use - they can fail, catastrophically, without warning. Do you have any recent backups of the home directory? I suspect your only chance is…
-
You've now changed the question again, introducing new things before explaining what was wrong with the original. It is totally unclear what you are trying to do, or where you are in the process. You've now pointed us at a Cloud add-on, but you look like you're working on a Server install. So, please, keep it simple and…
-
A project type is a project configuration, not user. A project is only of one type. There's nothing to stop you having different projects of different types for different reasons.
-
Add them to the user directory if they are not there, then put their account into the "can log in" group (see Admin -> Global permissions to find out what group(s) are in use for that.
-
Steps are the structural part of a workflow, which are hidden from the users when they are in the diagram mode. They are mostly hidden from users on the front end as well. There's a 1:1 relationship between steps and status - every step has an associated status, and that status can only be used by one step in a workflow.…
-
The data might change, but if two issue types don't have the same fields, you can't change between issue types by changing the issue type "field".
-
But that would be dual voting. You've already raised it, and that's your vote. To make multiple votes actually useful, you'd need a different voting system. Pool votes for example - across the system, you'd get 20 votes. When you've voted 20 times, you can't any more, until an issue you have voted on is closed, then you…
-
Both of those solutions are good, but they are both Server solutions. Only Atlassian run "Cloud", 3rd parties will run Server for you. You just need to decide if you want to host the server yourself, or want to hand it over to a 3rd party, and if so, what level of support you want to go for. There are plenty of expert…
-
For the background, there's no reason for Jira to do it. If you are changing issue type on the edit screen as a field, then the source and target types are, by definition, configured to use identical fields and workflows.
-
Without add-ons, yes, you need to subscribe to filters. That will not affect the "email as it happens"
-
We are trying to help you, but you do not appear to be doing anything that we are suggesting that you try. Please, tell use where you are stuck and where you have done something differently to Atlassin's docs.
-
In theory, you can, but it will be clunky and ugly, as it will need to include all the .net libraries and frameworks you call on as Confluence doesn't have any of them at all. It's written in Java. Your add-on will be far easier and better to write in Java.
-
You will need to install an add-on that tracks views, then you'll be able to ask that for the most viewed pages.
-
Jira does not have any "locking", it's an issue tracker, not a file manager. Access files might well be attached to it, but it simply accepts that any user uploading a new version of a file is ok to upload a new version without looking at anyone else who may have downloaded it and still be working on it.
-
Again, there really isn't enough log. We can't tell what the root error might be or if there are other errors.
-
There's not enough of the log to start there, we can't tell what the root error might be or if there are other errors.
-
This is a five year old thread, it's not likely to offer you a lot of help with a much later version. But, the advice from Septa still holds. Have a look at your logs.
-
How have you "created web item button"? If you've done it with a standard web-fragment, then it won't open in a new window without your code behind it telling it to.
-
I've never done it in a template. Never had any need for it. The one time I was asked for something like this, the actual problem the users were trying to solve with numbering was easily and better solved by using Confluence functionality that they were unaware of. I know the page id is available to pages, as I've written…
-
We're not support, we're a community of end users. My understanding is that Atlassian are not going to change this back, the architecture is not able to support it (in favour of supporting other stuff they do want to do)
-
I believe it compares the whole timestamp it gets from the database, so yes it would, although I didn't think Jira bothers to save seconds.
-
Use the "forgot password" links on the login page to get in.
-
Natively, no, the page title is just a string, given by the user, there's no way to inject something in there even with a template. You could use some code that could re-write the page title as it is saved, I think, but you'll need an add-on to do it, but you might find it struggles with the uniqueness and incrementing if…
-
If you don't know what went wrong with an installation, then re-installing probably isn't going to help you much, as you'll probably do the wrong thing again. But, yes, remove everything first, in case the problem is in a file that a new Jira install won't replace or update.
-
What does the log say the problem is?
-
It will, if your add-on uses a standard web-fragment to insert the button.
-
Those errors are consistent with Bitbucket not being able to read/write/execute/delete files in its installation and home directories, although it might also be a failure to reach the database. Check the file and directory permissions, as I suggested before.