Comments
-
This makes no sense. My guess is that you might mean that you want to add a new status into the workflow for bugs? Is that right?
-
And the page tree?
-
Duplicating issues generally isn't good practice, as you end up with divergence on the duplicates, and most of us don't need or want that.
-
I suspect you are in completely the wrong place. This is a place for the users of Atlassian software, not a medical forum.
-
What do you mean by "auto search"?
-
This is a six year old post and things have changed a bit. You might want to start a new question thread for a more up-to-date conversation.
-
The atlassian-confluence.log lives in the home directory, not the installation. Try <confluence home>/logs
-
If you have done a standard install, then Jira will be running on port 8080, so are you connecting to http://<your server>:8080/ ? What do you get in the browser when you try that? Also, check where jira is running with "netstat -plant" if you don't get anything on port 8080, and then read the application log to see if it…
-
Not natively because free-text fields are by definition free-text. They're not expected to hold limited options from a pre-set list, they're intended for data that in a pie chart would simply return a chart made up of slices of 1 item (one for each issue) If you're willing to code, script or use add-ons, there are ways you…
-
You'll need to adapt your model to allow for the use of Atlassian accounts if you want to use Cloud like this.
-
There's not going to be any way to change this. Users own their Atlassian accounts.
-
Get Portfolio and have Theme or Initiative -> Epics -> Issues -> Subtasks
-
No, it's not possible without changing code, and breaking the rest of the layout
-
That's a 7 year old video from a version of Confluence that has not been supported for years. You don't need a "rich text" option any more - the editor since Confluence 4.0 has covered it. To get the button thing, try installing the Content Formatting Macro, or writing something with a user macro.
-
I've not tried to use GO with Jira yet, but it should be the same as any other language - use the REST API to query Jira from your code.
-
Jira has many types of "custom field" available for your admins to add to projects (and you can add many of each type). One of the types is a multi-select.
-
Hmm. I remember this question being written in the first round of question writing, and I think I know who wrote it. The text of it has been changed since we passed it through peer review (possibly by the non-expert reviews on simplifying language, which seems to have broken a number of questions). The text of the question…
-
You can't make your boards public, only projects. Anonymous users will be able to create and comment on issues if you grant the "anyone" permission in the project. They'll be able to search like everyone else, and only see issues in projects with "Browse project: anyone". Voting won't work, it relies on knowing that an…
-
Depends on what you want to do with the data and the structure you want to load them into. We can't help you much with the add-ons you have tried with just "they are not working"
-
Click on the "breadcrumbs" at the top of the page, or look in the page tree.
-
That's correct. Create page and Edit are the same permission.
-
It's the same answer - you need to work out what your system is doing. Work through the points Florin and I made four years ago.
-
There's some useful references as to why it is this way, and why a lot of functions will never be available over REST over at https://confluence.atlassian.com/jirakb/user-management-rest-api-changes-in-jira-cloud-858756548.html (It's because the accounts do not belong to the Cloud site any more, they belong to the users)
-
Yes, it ignores the read-only flag on re-configuration. It's not an edit, it's a structural change.
-
The only issue type that I would not reconfigure is "Epic", if you have Jira Software. The rest of them are, as Warren says, totally configurable. If your users decide they want to call an issue type "Penguin", then they can. (I use that because I have worked in a place where it made sense!) You're right with status as…
-
Permissions are not associated with users, so no. Even if they were associated with users, I'm not sure how you'd expect to edit something that was not there. I think you need to explain the question a bit more.
-
No, that's wrong. A role is a global thing. When you add a role, it becomes available to all projects, permission schemes and notification schemes (although they do not have to use it) In the permission scheme, you can say things like "Assignable user: Any one in role X". This does NOT grant any access, it is just a set of…
-
It's the right-hand column. That is not configurable. For your case, your best option is probably two boards. One scrum with Accepted as the last column and then a Kanban for moving from Accepted to Released.
-
I would have said that, but voting doesn't tell me who voted (it is stored, so I can get to it with code, but not with plain Jira)
-
Multi-select list of "interested clients" on the fault? Or if they are Jira users, the watcher list?