Comments
-
Stick to REST queries, they're far more easy. If you must do it with SQL, then you need to read the cwd tables. I think it's app_dir ones to work out what groups have access to stash, then the cwd_membership table to get a list of users in those groups, then cwd_user to check each user for their "enabled" flag. Then for…
-
I don't think there's a debate here. Kanban is a lot more simple than Scrum because there's less process behind it, and a lot less data on the board. Everywhere I see Scrum and Kanban boards used alongside each other, the Kanban boards are always vastly more simple than Scrum. But I don't see them as being particularly…
-
Your best option is to throw the SQL queries away as they're going to be different for every board, and change all the time. Use the REST API instead.
-
The relationship between a board and an issue is defined by the JQL used on the board and then filtered by the settings for the board (if you're interested in columns, swimlanes, quick filters or the Kanban board's "definition of done") Your database query is, quite simply put, going to be horrid to construct and valid…
-
Possibly. Have a look at the queries being run - I would expect to see indexing running many sequential reads while running, and then revert to relatively low usage afterwards, writing issue and settings updates as users use Jira and reading when issue views or certain types of query happen (the index and caches are used…
-
Go to board settings -> columns, you'll be able to add, remove, rename and rearrange columns, and drop status into them.
-
Do you realy run Confluence as a user called confluence.confluence, or are you trying to set the ownership and group to confluence and confluence? If you are trying to set ownership and group, try confluence:confluence instead, not a . to separate them.
-
No. You need the built-in field called "resolution" to be used. It's always there, but I would guess that you have removed it from screens and/or used the field configuration to hide it. It's fine to hide it, but if you do, you *must* set it with post-functions at the very least, to enable Jira to know when things are done.
-
It's the other way around really. Kanban and Scrum both represent your issues as cards on boards, split into columns which are groups of status. You move cards between columns to show status updates, and consider cards in the last column as "done". Kanban has a simple "clear the last column button when appropriate" Scrum…
-
The owner for the directories should be the user who is running the service. For example, on my server below, I've given ownership to charlie. By default though, Confluence and Jira installers will create dedicated users Jira and Confluence, and you should make the directories owned by their dedicated users. To do what…
-
There is something wrong with the settings on your SQL server. A simple indexing from Jira might cause high load (as it reads every single issue in the database as fast as it can), but it won't crash it. It's not doing anything other than reading. If your database can't cope, it's a problem with the database.
-
There is no link. This is one of hundreds of reasons you should forget SQL when looking at Jira - it is the worst possible approach to doing anything in Jira. To explain why there is no link between issue and board in the database, it is because you do not need one. A board is a view of a set of issues, which is determined…
-
Same as above - if you're sharing the pages, you must trust this person, so make them a user, or make the page anonymous. (Or scrape it and send separately, bypassing your security policy)
-
From scratch, and assuming you have a project with tasks and bugs that should have different screens: * Create some screens to work with, let's say you create bug-view, bug-edit, bug-create and task-view, task-edit and task-create * Create a screen scheme called bug-screen-scheme.* Associate bug-view with view, bug-edit…
-
Ideally you should make them exclusive, to avoid the problem. The problem you describe with it confusing your users is actually worse if you allow a card to be seen twice - people start marking things as duplicates and complaining that changes to one affects the other. I'm afraid you can't change over to show multiple…
-
It's the first line in the troubleshooting section on the page Aswin linked to.
-
Ask the admins of the current system for the "developer licence". That will save you having to use a trial licence that will expire.
-
No, there is only one time-tracking field (even with add-ons) People do log work separately though, and Tempo can help you see that.
-
Admin rights in Jira are granted by being in the admin groups. The doc covers adding your account to an admin group.
-
As you were offered the delete option, yes, permissions are fine. That error is to do with the ranking being broken. If possible, re-index the project the issue is in, and run the integrity checker too.
-
Start with https://confluence.atlassian.com/jirakb/jira-applications-system-plugin-timeout-while-waiting-for-add-ons-to-enable-212173447.html
-
In the days when corporates had decent internet and most households did not, my teams used to go to (or stay in) the office in their own time to play multi-user games. Now most of us have at least ADSL, we do it from home more.Gaming is about the only thing you can do with teams on-line, as far as I can tell, unless you…
-
Yes, there is a bit of a problem. Jira has a simple flag for "resolved" - if the field is empty, an issue is unresolved. If the field is filled, the issue is resolved. That logic affects dashboards, reports, searches and the display of issues in a lot of places. You need to make your workflow and edits account for that.…
-
I don't know enough javascript to tell you. (I don't bother with javascript because it's usually a pointless thing to do in Jira, it's something I tend to strip out when asked to make Jira work properly, and always recommend not doing)
-
Ok, then cf = customFieldManager.getCustomFieldBy<something-type>(<something-name>) issue.getCustomFieldValue ( cf ) is the right approach. You'll get an object back which is of the type of the stored data (string, option, date/time, number etc). The <something-type> would be "by name" or "by ID", and you need to feed it…
-
The problem for Atlassian is that there's no way to write a generic rule that suits all their clients. So they leave that to the users to come up with and code for their own rules.
-
There is no way to administrate a Service Desk without Jira administrator rights, they need the same access.
-
Sorry, I missed this first time around. Jira has now way to know what you want to link to unless you tell it. Off-the-shelf, there's a simple solution - use a "url" type field and ask your users to put it in there. Or, better, ask them to use the "link" function (it's not just for linking to other Jira issues) For what…
-
Yes. The field is provided by an App. Your Jira has not had a licence for it installed, so the App does not work. Get a licence from your my.atlassian.com account, and click on your "configure licence" link to paste it into your system.
-
To answer your question as stated, custom-field-value.equals("") In reality, that will not work, because an empty custom field is not "" or even null, you will get a not found error as it doesn't exist at all. In that case a simple "(if custom-field-value)" will do the right test for you.