Comments
-
You can't do this as stated because a user either has an account or they do not. There are three ways an individual can see Confluence content: * They have an account that has "browse" access to a space * Anonymous access is enabled (which means the user does not need to log in, but you can't tell who they are) * You have…
-
The link does not require a login.
-
You need to explain what Sigeri is and what it has to do with Atlassian systems?
-
Yes, replace jira.mycompany.com with whatever you have on the "server" line in your nginx settings. Note that you will need to have set up that url in your DNS too.
-
See https://confluence.atlassian.com/pages/viewpage.action?spaceKey=DISC&title=Show+the+content+ID+(page+ID)+in+a+page
-
From that nginx config, I would say you need to visit https://jira.mycompany.com to see Jira.
-
Possibly. There are lots of test management apps for Jira in the marketplace, most of them add an issue type or set of issue types for tests. Or you could create your own if you don't need the power of those Apps. To add Zephyr (or others), go to Admin -> Find new add-ons and search the marketplace for them.
-
Correct - this is breaking your system because it means "resolved". Jira does not know or care what any resolution option's label is, the rule is "field empty/null = unresolved, field with any value = resolved" I would first change the name of "unresolved" to "broken resolution - do not use", that will fix your searching,…
-
Right, so gmail suspects you are spamming. Have a read of the link that they gave you in the response.
-
Yes. If you want the old UI, move to server.
-
No, Comala's workflow functions are outside the "edit" function.
-
Confluence does not have a workflow engine in it, and hence there's no status in it. I think you might want to add the Comala Workflows App to get workflows.
-
Same here. One of the targets is currently asleep on my leg, next to my 'phone.
-
Only issues that are fully done will drop from the backlog when you end a sprint - that means they are in the right-hand column of the board and all of their subtasks are as well.
-
The pages don't have limits that would give you this error. There is something wrong with the file system and Confluence can't write to it. The most likely causes are either a permissions issue or your disk is full (there may be other issues, but those are the two we see most often)
-
>Can jira solve it by allowing me to map 1 status = 3 columns? No, because that's nonsense and doesn't meet your use case at all. The columns represent different points in the workflow. If you had a status in more than one column, the board would be telling you two or more contradictory things. I think you probably mean…
-
I'd guess that you've set a fix version on the missing issues, so the "filter out done issues" is hiding them.
-
No, once you stop paying for the system, it is shut down and deleted. You could export everything to a backup and then restore it when you restart and buy a new system, that's the closest I think you can get.
-
That suggests you haven't got any "Sub-task" issues defined. Could you pick one of the 2000 issues you say it should be showing and look at the project and issue type?
-
That app is only for Server/DC Jira installations, not Cloud. For Cloud, you have to download the whole system, merge and re-upload the resulting data set if you want to do a complete merge, or configure your project manually and import the issues from CSV.
-
Then the board is dropping them because it's supposed to - in Scrum, done issues will only show for the current sprint, in Kanban issues that are "released" (as defined by the sub-filter) don't need to be on the board, so they're hidden, and business boards drop the issues 2 weeks after it has been done. Or you have…
-
That sounds like someone renamed Sub-task so the search does not find it any more. Have you tried retyping the JQL and accepting the auto-suggestion it makes as you type sub-task ?
-
This error will be in the log, I suspect you are looking in the wrong one. Which log(s) have you checked?
-
Then your performance tests are wrong, or you are using really under-performant local disks. The performance of your disks is not that important though, you're measuring the wrong thing. You need to measure your Jira performance and the error rates you are getting (these should be zero on local disks, but won't be on a SAN)
-
Because humans like a natural language summary of the thing they're working on. A short, unique, space key is very useful, but a description for it can be essential. Imagine you've got a space for sharing stuff on your current project, and you work for a large organisation with naming conventions and a lot of existing…
-
Without rewriting Jira so that it has global versions, there's nothing I can suggest here. Versions are done by project. If you want a set of issues to use the same versions, they have to be in the same project.
-
They are not "duplicate" columns. Each version is separate and gets its own column, so each column is rightly representing one individual version. The add-on you've found synchronises between separate versions, not makes them the same thing (you'd have to rewrite a chunk of Jira to do that)
-
You need to use a transition that exists and your user has permission to use. This depends on what status the issue is currently in and what your workflow says.
-
Then you can't delete because you must have someone named as the owner.
-
What white paper and where are you stuck?