Comments
-
Errors would be logged (unless you've turned it off in "logging and profiling", which I would not expect most people to even know about, let alone use it!) I'm afraid without a deep look into your system, I can't get any further. I'm sure it will be something I have forgotten, but we'll have to wait for support if there's…
-
Scripts are stored in the database, unless you configure each one to be read from the disk (in which case, they're under <home>/plugins/scripts by default). I cannot remember if it lets you store behaviours on the disk, I seem to remember not, as there's a lot of config around them in the UI which stays in the database.
-
Repeating the question with no new information does not help. Please explain what "integration" you are doing, how you are doing it and what is going wrong.
-
But that's not how a scrum board works - it doesn't (and shouldn't) care about the status in the backlog, that's not what it is for. This is one of the downsides of trying to use both types of board, the difference between the way they need to work must be understood by the people using them. Scrum boards do not need to…
-
Only if you have added Jira Software to it as well.
-
Confluence does not have a direct "file library" function. You attach files to pages, and then use macros to list them if you want a library effect. Can you explain what you have that you think of a "file library"?
-
I'm afraid you will need to tell us more if you want help. "not loading properly" does not tell us anything.
-
This means you have a field called "phase" which you have configured to be mandatory in this project. You will need to put it on the "create" screen and get your people to fill it in, or make it optional.
-
I am afraid there is too little information here for us to be able to help you. What is a "sakai 19"? What are you building, and how?
-
Yes, see the answer before!
-
Is this server or cloud?
-
I'm afraid it is. It is a security hole to continue sessions. You are right that the user experience is absolutely critical - "not being hacked" overrides "slightly more convenient" every time.
-
What "integration" have you done?
-
Oddly, I can find it in the installation docs, and the healthcheck docs and the troubleshooting docs. For example, https://confluence.atlassian.com/doc/database-setup-for-sql-server-9258.html
-
There are loads of tools for customising Jira, just have a look in the marketplace. And you can write your own of course.
-
Because it is supposed to record the estimate you made first, and then track changes to the estimate as updates, without losing what you originally said. It's not messing with your reports, it's telling you what was changed.
-
What makes you think they are not added to the project? Could you show us the list of people in the project?
-
For what?
-
Welcome to the community! I would start at https://www.atlassian.com/software/jira/guides/getting-started/basics to get going with Jira
-
That is a different problem. If there is a value in a field and you get an error trying to save it, you have a validator going wrong. Could you ask this as a new question and give more detail on the field config and fields on the create screen?
-
It's the "platform" point that I think matters here. Jira itself has no SSL capability, and it should not have to. It runs on a platform (or actually a couple) that should be handling the SSL. When someone asks about SSL and Jira, there are two sides to think about - outgoing and incoming. On incoming, I don't think…
-
It depends on why they "disappeared". Do you mean they are no longer on the board, or that the user cannot see them at all, or that they have been totally deleted? To establish this, first have a look at one of the issues - forget the boards, just go straight to the issue (e.g. if you've "lost" ABC-123, go to…
-
Correct, removing the board won't have removed the issues or amended the other board. Deleting a copy won't affect the issues (other than removing the "issue is on board x" links)
-
Deleting a board will not affect the issues - remember the issues are not "in" boards, they're just "looked at" by boards. There's no way (without going to a backup) of getting a board back. Are you sure you only deleted a board, and not a project?
-
Have a quick look over https://bobswift.atlassian.net/wiki/spaces/JCLI/overview and then follow the link to "getting started"
-
You need to make the source page available to the people who should be able to see it.
-
Plugins are global - if you're working in the same Confluence, you have the same plugins. I suspect that the problem was that your team-mates had not granted you access to the reports.
-
Correct - because a board is looking at an object, if you change or delete that object, it's changed/deleted in all the other views too. You can't "move an issue from one board to another" - issues are objects that the boards view. You need to create separate tasks for each team and then create views (boards) for them that…
-
Boards do not contain issues, they are a view of a set of issues. Projects are the issue containers. If you do something to an issue on a board, you are affecting the issue. If you edit it, transition it, delete it, the change happens to the issue. Other boards will show that change because they are only a view.
-
No, that would breach the security and permissions model.