Comments
-
Sounds like either your id was not in the old user database with that password, or there is a fault in the user directory. Read the log to see what is happening when you try to log in.
-
There's no function to do this in JIRA, it's not a documentation system. If there were, I'd imagine it would be the same as Confluence's history as well - not shown inline, but a history of revisions, which is roughly what you get with the default history already - it's just that is a flat from->to, without highlighting.
-
No. You must be using Innodb tables. However, this is just a warning that your defaults are not suitable. If your tables really are all Innodb for the confluence database, you can simply ignore it.
-
I'm afraid I don't understand that. My question was trying to establish the symptoms you see when you are using the various workflows you have mentioned. However, I would like to rule out the "unmapped status" - can you put *all* status into columns and then check if you still have 4 missing subtasks?
-
That's not what I asked. Are you changing the underlying database? e.g. the source was Oracle and you are importing into PostGreSQL?
-
The add-on does not have a reset, so I'm afraid you are stuck. I'd read the logs to find out what is going wrong there, and if it's not really obvious from them, contact the vendor for support.
-
There's an update rolling out (maybe fully rolled out?) that removes the need for end-users to have any access to re-index.
-
My instinct on this is automatic sub-tasks. Where you place them in the workflow matters a lot though, and needs to be matched up with your real process. Most of the "onboarding" type workflows I've worked with in the past are set up as a "story" type issue. When the user creates the initial issue (representing "we need a…
-
Could you post that as a new question, and with a full problem description? Necroposting out of context reaches a limited audience and gives us too little to work with.
-
If "restore defaults" does not get it back, then your administrators have changed the defaults. You should get them to add the status proper back to the defaults. I'm afraid that's one of the only two option now, recent UI changes have broken the work-around. The other option is to address your "fielditis", as Tyler…
-
Ah, @MoroSystems Support has corrected my point 2 - there is a 3.5.17, but listed very out of order (it was a retro-fix that was released after 4) However, my first point stands. Please have another read of it, and explain what you don't understand if it does not make sense?
-
Yes, the workflows and screens are configured on a project/issue-type basis. So a workflow scheme says "in this project, use this workflow for issue type A, that for B and something else for all others". A screen scheme does the same. To get different screens on create or edit, you have to be using different issue types.
-
If you're using Kanban backlogs, you can put multiple status into it.
-
That's never going to work, it's just not what Confluence is structured for. Try the macros "include", "excerpt-include" and "excerpt"
-
If it's not that, you'll need to read the logs for more information
-
Sort of - it's a bit more complex than "it automatically re-indexes", it's more like "the indices have been changed so that only minor changes need to be made when certain changes are made, rather than huge re-indexing of everything every time"
-
1. You have not read the question or answers properly. Again - if I have a user name and password and I want to log into JIRA, which one? How is Atlassian supposed to know which one of the hundreds of thousands of installations I have an account in? (Especially the ones firewalled off from them) 2. In one part of it,…
-
My instinct was that the requirement is to hide "done" sub-tasks on stories and issues. But you're right, it's not clear.
-
That is a well known symptom of the JIRA server not being able to reach itself over your network. Check routing, firewalls and name resolution are all correct, and allow Jira to talk to itself. If they are all fine, then the next thing to check is SSL - does the server have the right certificates to talk to itself?
-
Ah, good, that's the first solution I would have offered!
-
It's not an issue field, so you can't fill it in for issues, so it doesn't appear on Create.
-
Try it again, Atlassian monitor this stuff and try to fix it as quickly as possible.
-
Are you on Cloud? You can't create user macros on Cloud.
-
Most data is added/changed on issues with the MutableIssue object, but with things like links, you'll need to use the relevant "manager" objects (IssueLinkManager for example) See https://docs.atlassian.com/jira/server/
-
This version of it is based on the Lithium forum software.
-
Ok, are you changing databases with this import?
-
Again, you have to duplicate their accounts on the SD server and grant those accounts access.
-
It is a lot better. Or you lose information.
-
Check you have "delete attachment" permission. Then delete it. Be warned that delete removes it completely - any mistake and you'll have to go to backups.
-
That is a better option :-) The lead really should be the owner of the project!