Comments
-
Status is an indicator of where an issue is in the workflow. Resolution is a field on the issue. They are not really linked in any way in the code. As an admin, you need to set the workflow to handle resolution for you - either use a post-function on transitions into "closed" or "resolved" status, or use a screen that…
-
To support what Jamie says, most of the instances I've worked on are way over 200k, and are mostly working fine. Things that do help when the systems start to struggle - better hardware, tuning the users (getting them to stop hitting it with hundreds of large xml queries or downloads), tuning the memory, and upgrading…
-
Not natively, but there is a plugin - see https://studio.plugins.atlassian.com/wiki/display/JDVP/JIRA+Database+Values+Plugin
-
I'm afraid you can't do partial searches on select lists - you have to search for each option you want to include.
-
No, but yes, sort of. We can't actually answer that. It depends entirely on what your Product and Team users need from their projects. Your assumption could well be correct for your users, but it might not work for other sets of users or other organisations.
-
I think you need to explain this in more detail and in language that actually refers to JIra. What are you trying to do with fields and "actors" (I guess you mean users?). Not a clue what you might be talking about when you say "anchors"
-
No, as I said, you lose access to the issues in that status because you've removed it. Remember that the board is a visualisation of a pile of issues. If you choose not to display something, then it's not on the board. You need to decide simply whether you want these on the board or not.
-
You can't "hide" a column - if a column exists, it is shown (it's pointless not to show a column if it exists) But, you don't have to have a column. If you unmap the new status so that it is not in any column, and then remove the column from the board, you'll have the desired effect. Problem is that you won't be able to…
-
I don't know what report it is or how the permissions might be done. The reports in plain JIRA don't have any permissions to run them, so I don't know where that comes from (but they may return no data if you don't have access to the issues it tries to report on)
-
Ok, that's pretty clear - you don't have the right access to see the report. Check the privileges you have on it.
-
It often means a user has been deleted when they still have data in JIRA tied to their account, or you're trying to work with a non-existent user. But, where exactly is this error occurring? You say "report" then "insert my user", but we need to know exactly where this is - there are a lot of reports in JIRA.
-
What is the problem? You've not explained why you are not deleting the page
-
Oh, and make sure it's a top-level issue you are trying to convert to a sub-task - there's only two layers, so you won't be offered the convert option if it is already a sub-task type (you will get "change parent" in those cases, for moving it under a different top-level issue)
-
It's on the issue view screen, not the menu. It will only appear if the project has sub-tasks enabled (which is pretty obvious if you think about it - no point in showing it if you can't create sub-tasks in the proejct)
-
Hmm, ok. Bit of a long shot, but do the sub-tasks all have the same workflow and fields defined?
-
Nope, it's all still there in 5.1 When your users say "they can't", could you get them to expand on what they're seeing? Do they have the option at all? Or does it fail part way through?
-
Ooh, I've seen that happen before a few times. It's silently failing to remove them from the group. In my cases, it was different causes, and I had to read the log file to see what was going wrong. (As usual, tail -f the log file while clicking the "delete" in another window)
-
Yes, they've closed the real one as a duplicate of an issue that doesn't really describe it. The one that has the most information is https://jira.atlassian.com/browse/GHS-9720
-
There's a known flaw in the design of the boards - you can not drag between status in the same column. Atlassian have it on the road map, but I don't have the reference to hand.
-
Your mail server is not responding to the JIRA server for some reason. Connection reset can have many causes, but it's usually incorrect credentials or a firewall blocking access. You should be able to read further through the log for more information on the error.
-
Same answer, except that you have ruled out the "field not there" case.
-
You have tried to change the sprint field on an issue. The field does not exist for that issue, or your account does not have the edit or manage sprint permission needed to change it
-
There's not a lot more we can tell you. You have tried to change the sprint field on an issue. The field does not exist for that issue, or your account does not have the edit or manage sprint permission needed to change it.
-
Oops, sorry, yes. There is an equivalent url for the main page view. Confluence tries to use "pretty" urls when it can, so pages named like "my page" are available on /display/space/my+page, but the physical ID of a page is always available. Try /pages/viewpage.action?pageId=123456 instead.
-
Use it in the url e.g. https://confluence/pages/viewinfo.action?pageId=123456
-
No. You might be lucky and be able to simply edit the version in an export, but it's not supported, and you may need to amend quite a lot to make it all work. That is why you do not use early-access or beta software for production. (For what it's worth, I've got a 5.0 early release dataset to import fine in the 5.0 real…
-
I am sorry, I do not speak Japanese, so I am relying on translation software. It sounds like you have added work logs which are incorrect. You should be able to delete them and restore the time logged back to zero. You need to make sure you have "delete work log" permission in the project.
-
Short answer then - no. You cannot have Parent issue types as sub-tasks. All issue types have to be parent or child/sub-task and you can't use one as the other. The structure you've posted looks like it's three levels as well. Jira only has parent and child/sub-task. You can't do anything about that. However, the…
-
The warning is telling you what is wrong - you need to make the "missing" issue types the same as the others that you can create. Although, the way you've written the question makes me want to check one other thing - can you confirm that you have set up "story" as a type of sub-task and not a top level issue type?
-
I apologise for not being able to write in Portugese. I think you need to define what you mean by "better". They both have strengths and weaknesses, which leads us to ask "what do you want to use them for?" before we can answer properly. See…