Comments
-
See https://community.atlassian.com/t5/JIRA-questions/Every-one-should-be-able-to-create-ticket-But-can-be-edited-when/qaq-p/598900?posted=598937#U598937 You are asking some very basic questions here that strongly suggest that you have not used JIRA or read any of the documentation, and you are repeating them. I'd…
-
You will need to get your administrators to edit your workflows.
-
See https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html
-
Yes, you can do this, just let these users browse watch issues, and give them no other roles in the project.
-
See https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html You will then need to change the screens your projects are using, so that some fields only exist on the "create issue" and "transition" screens.
-
Use conditions in your workflow, then have a look at https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html
-
Have you modified the email templates?
-
See https://confluence.atlassian.com/adminjiraserver071/configuring-issue-level-security-802592414.html
-
A column is a collection of one or more status, so your CI simply needs to push the issues into a status that is in the column.
-
I suspect your issues were not in the right-hand column of the board when you closed the sprint. Issues that are not in the right-hand column are not considered "done" by the board, so they will go to the next sprint or into backlog when the sprint is coled.
-
Duplicate of https://community.atlassian.com/t5/SourceTree-questions/sourcetree-in-mac-doesnt-start/qaq-p/598817
-
If you're happy for everyone to get the same home page, go to Admin -> Further configuration and choose a space in the "site homepage" box. This will make the default landing home page be the home page for the space selected
-
Start at https://confluence.atlassian.com/cloudkb/pros-and-cons-of-cloud-vs-server-691011844.html The main reason we find people migrating from Cloud to Server is that the Cloud is a lot less flexible.
-
The curl command you've given works for me on a Mac and Linux, so I'm not sure that you've given us the exact curl you are using!
-
A project is a container for issues. It's not an issue. Two simple options not requiring code: 1. Group the projects together in a project category 2. Use one project, using components (or a custom field) to represent the sub-projects
-
Most good Atlassian consultants do lurk here, but you might want to try standard job sites as well, and of course, linked-in and Xing.
-
The reason it's possible is simple - it makes perfect sense to have parts of a story in different status. Consider a story like "build a house". The sub-tasks of foundations, structure, roof, internal walls, etc etc etc are almost always going to have different status. The foundations can be "done", where the main story of…
-
Two answers here 1. You have "fielditis" and you should fix it. You said "We have about 60 fields with the word project in them" which instantly tells me that you've let your users have way too many fields and your admins really need to do a LOT of system sanitisation. JIRA does let you add as many fields as you want, but…
-
I'm afraid not, that's a weakness in the 'bot, it doesn't know how to translate a field id into a field name. I don't believe there's currently a fix for it.
-
The two URLs represent two different aspects of JIRA, ones that expect different types of user, and the sign-up options need to be different. The main login is for JIRA users, those who will be using projects, issues, boards, agent functions and so-on. By default, self-sign-up for them is generally turned off, but you can…
-
https://www.atlassian.com/experts is a good starting point. Asking here is another good route - not all consultants are tied to the Solution Partners.
-
JIRA is written in Java, so add-ons are easiest to write in that.
-
Yes. Install the JIRA Software application. On server, from the "manage applications" admin section. On Cloud, it's available in your my.atlassian account as well.
-
How often does this actually happen? I ask because a broken index is something that should be very rare. If your users are seeing this behaviour regularly and frequently (more than once every 6 months), you have something very wrong in your system and you should be fixing that.
-
You need a condition here, one that says "if resolution is done or fixed". A condition will stop the user using (or even seeing) a transition when it is not matched. I don't know of an off-the-shelf condition that will check the resolution, but there are plenty in add-ons that can do it.
-
No, labels are built to be free-format and allow all users to define new ones. For a fixed list, your admins can give you a multi-select list. Components are the closest you'll get, with project admins able to define that list.
-
Changing a workflow requires JIRA to do a whole swathe of integrity checks that can often lead to a load of questions needing to go back to the user. A REST interface for that would be hideously complex and barely ever used, so Atlassian have not written one. The answer for your usage really is what Thomas said - use a…
-
I'm not sure what the question is here. The column is empty because that's how JIRA works. You should not be changing anything in the database with SQL, so the answer to "how can I update this columns in oracle" is "do not".
-
Duplicate of Duplicate of https://community.atlassian.com/t5/JIRA-Software-discussions/The-PKEY-is-null-in-JIRA-db-Oracle-in-table-jiraissue/m-p/598539#M35
-
Duplicate of https://community.atlassian.com/t5/JIRA-Software-discussions/The-PKEY-is-null-in-JIRA-db-Oracle-in-table-jiraissue/m-p/598539#M35