Comments
-
Ah, no, the point of "none" is to explain to the user that there are no components associated at all. In the database, there's no data at all for "none". From a database/Jira point of view, the logic is: if no nodeassociations for components are find, display "none" I'm sure there's a way to pull that out in SQL, but I'm…
-
(Sorry, I'm not a DBA and don't really think in SQL, so I didn't try to unpick your SQL and add that in as I'd probably get it wrong - I think the general concept is more useful to you, and you can make a neater and better job of using it than I would!)
-
You need to read nodeassociation (for the links to components) and the components table (for the data about the component) Include something like this in your query (which is a copy and paste from the docs - https://confluence.atlassian.com/display/JIRA041/Database+Schema#DatabaseSchema-Componentsandversions ) select *…
-
What does the log file say?
-
It wasn't a very friendly question - it's a sentence as a title, with no explanation, and the language is totally unclear. Also, I'm not support. We're a community of end users.You have improved it, but there's still no such thing as "steps" in issue view, and you've now mentioned project, so I still don't know if you…
-
I'm afraid that's nonsense. What do you mean by "status step", what visibility and why are you looking at jira-config when it's got nothing to do with status. My best guess is that you want to see more transistions in your issue view, so you are tinkering with the workflow setting in the properties file. Which is global of…
-
No. You can't even do it in download, without some coding.
-
I wouldn't bother. The priority is a more important field than severity for classifying issues, and you'd be better off simply adding "Severity" as a custom field. Priority, as implemented in Jira, has a load of functionality around it that doesn't really apply to severity levels, so you'd be losing potentially useful…
-
You can change the general wording in Jira to match your concepts by following the stuff at https://developer.atlassian.com/display/JIRADEV/Customizing+Text To add an additional field, quite simple - use a custom field. https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field Personally, I'd warn you against…
-
I'm with Adrien on this, the Unix guide works fine for Mac installations. It's a little bit of a different file system, so if you don't want to use the default locations, you have to understand how Mac's organise the directories, but everything else is so close to the Linux guide, you won't have any problems.
-
I think you're asking for some form of security that says "a reporter can only see the issues they reported" (and probably your internal team) There's two ways to do that. The clumsy way is with Issue Security levels (clumsy because you have to remember to set one every time). A better way is "reporter browse" permission -…
-
You could script it over the REST interface, or use an add-on like Bob Swift's CLI to make that easier. Or try out a script in the Confluence Script Runner add-on. To avoid scripting/code though, try WebDav - https://confluence.atlassian.com/doc/use-a-webdav-client-to-work-with-pages-200704169.html
-
In the absence of any other answer, I'd say "we don't know". For your questions, I'd start with:1) What have you tried to integrate? (i.e. what have you read and what is it supposed to do?) And where are you stuck?2) Possibly. I'd use a post function to update desk.com, probably, but I don't know what the integration is.…
-
It is unlikely that you will have enough memory installed on your server for this to work.
-
Those tools do two very different things, I probably woudn't bother.
-
Still curious as to why you need to export by the way. There may be a better solution. Oh, and tables, you'll want to look at https://developer.atlassian.com/display/JIRADEV/Database+Schemafor the full schema and how some of the bigger stuff hooks together. Bear in mind the schema varies between versions of Jira (but not…
-
Yes, you are absolutely correct I said it in the first sentence, but re-reading it, I can see how it's unclear. I fall into odd English ways of phrasing things sometimes, and it makes my prose unclear. Sorry.
-
Sub-tasks are still issues in their own right. I avoid the use of SQL because you have to build an understanding of the data structure for it to be useful, and you shouldn't really run it on an active Jira database - there's the risk of constructing queries that cause overloads and take your Jira out. (and it also makes…
-
My memory isn't strong enough to remember the exact versions of Agile that Sprints were implemented in. So, go to "Agile" and click "create board". Are you offered the option of "Scrum or Kanban"? If not, then you don't have a version of Agile that implements sprints.
-
It really does look like a simple failure to find the server based on the url (whether text or IP based). The logs look healthy, I'd expect everything to be running from them, and the error message is pointing at DNS/networking, not the server.
-
I think you need to think of a different way to arrange your data.
-
When you set "swimlane = story", there isn't really a query behind it. It takes each story with more than 0 sub-tasks and uses that as the header. You can't change that either - it's code, not a query. You can't do the grouping you describe either. A lane has a single layer of grouping, not two, so "group by X under Y" is…
-
I am sorry, I don't understand the question. You have a custom field (CR) on the issues, I see that. You want to do something with that field in swimlanes. But I don't understand what you are trying to achieve. You need to see the CR on the issues on the board? You are trying to do swimlanes by CR instead of Story? Could…
-
This sounds very confused to me. Your second paragraphs doesn't make a lot of sense to me - within a project, you can define any workflow for any issue type, but it's a fixed, one-to-one relationship. For example, Type A uses workflow 1, Type B uses workflow 2 and all the other types use workflow 3. It doesn't matter if…
-
Not sure why you have moved on to jira, you said the problem is happening in confluence. Anyway, as I already said (and what the error message says), the error is caused by the mail user not having the right settings to send the email in the email server settings. So yes, fix exchange
-
It's pretty much what it says - the user you've told Confluence to use as the mail sender has not been given permission to send mail on the mail server. You need to correct the configuration of the acount on the mail server.
-
The "create" screen is effectively an edit screen - try "Message Custom Field (for edit)" instead.
-
They won't appear on create because the issue has no data, so they have no data to display. You actually need a totally different type of field if you want things to appear on the create screen - some form of "message" field. There's one in the "Jira Toolkit" add-on which will do the job.
-
Make sure the read-only field(s) are on the issue view screens (no harm in adding them to create and edit as well)
-
You can't, that's not what fields are for really. Two workarounds spring to mind: 1. Put the field on the "create" screen only. The users will be able to override your default, but won't be able to change it later. 2. Add a read-only text field and populate that with a post-function