Comments
-
Something has removed or changed the ownership of files in the application's home directory. To avoid this, you need to stop doing that. Start with a check on the permissions. Are all the files in Jira and Confluence home owned by the user running each of the applications?
-
It sounds like someone has changed the board sharing settings, and managed to exclude some users. Have a look in the board configuration for sharing.
-
Ok, a slight change issuetype = StoryBug and sprint in (sprint 1, sprint 2, sprint 3, etc) Total count is up to the reporting you're using. I suspect you're going to need to write a report or gadget to get this out.
-
Three options: * Run Jira on port 80 (which will block that port for all other services on that server, including a web server, and is a bit of a fiddle to set up), * Use a proxy - the proxy runs on port 80 and can refer to Jira on 8080 when asked. This works really well with subdomains - mysite/jira, mysite/confluence etc…
-
The query issuetype = StoryBug and sprint = "name of sprint" should do it, but I suspect you want more than that?
-
Check the contents of your user directory and check the logs to see what and when it was updated (if it was. It does sound like something has changed on it, but we can't be 100% sure)
-
There is, but only Atlassian have it.
-
Now I don't understand what is wrong. If the field is showing "ready to verify" and it's a single status in the workflow, then it's showing you the number of issues in that status. I'm lost on what the error is. Could you give us an idea of the gadget configuration? The filter it is looking at, and what the fields for the…
-
What does the label for the second one say? The one that is a "sum of the other states"?
-
No, they're the same.
-
You need to wait for Atlassian to fix it on Cloud, and hide the projects when they're secured.
-
I'm not sure, there are a LOT of people who really dislike the new interface on Cloud. Atlassian need to get it right before inflicting it on Server users. Personally, I don't think it's any good yet. It doesn't expose the search properly, and the loss of the page tree in Confluence until you've gone four clicks down to a…
-
Did you sign up for Jira Core or Jira Software ? The boards are part of Software, so you need that. If you got Core only, then go to manage applications to get Software added in.
-
This forum software adds crud to the end of links - try the link again, but go to the url box in the browser and remove the control characters after the .html near the end.
-
The property blocks it because until you finish the transition, the issue is still in the status with the property on it. There's no workaround without code really, and even that's a bit clunky. If you add a new custom field for "next assignee", let them fill it in on edit, and then copy it into assignee in a post-function…
-
If you remove a field from the edit screen, Jira stops the in-line edit as well, as it wouldn't make senses to be able to edit a field if it's not on the edit screen.
-
Not quite. Every board has an estimation statistic. Issues can have hours in the time-tracking field and they can have numeric fields on them such as Story points. You can fill in these fields as your processes require. Then, you tell your board to use either the time-tracking estimate field OR a numeric field such as…
-
The database user (jiradbuser) does not have the full rights it needs to work with the database. You need to stop Jira, correct that, and restart Jira. Hopefully, it has not done significant damage yet, and just completely failed to create any damaged issues or parts of them.
-
You don't. The pie chart is built to display the information you feed into it, not part of the information and some other stuff you have no way of telling it.
-
No, custom user fields do not have the same functionality as the assignee field.
-
Jira logs all changes into the issue history, with a date and time. Is there something missing from that?
-
This is very odd, the error you get on screen should absolutely be replicated in the application log. A long shot next, but could you do the same for <jira install>/log/catalina.out ?
-
Ah, so it is working. The editor does not do wysiwyg in the version of Jira you are on.
-
No, I am sorry I was not clear, but I am not sure how to explain it. Click edit to get into edit mode. Double click so it is highlighted. Look at the editor bar above the text box. Click bold. Save your change. What do you see in the text when you re-read it after the page reloads?
-
Ok, could you explain "unable to format"? What happens when you highlight a word and click on the bold button and then save the edit?
-
The short answer is "yes, things can break". You should not edit a simplified workflow. You won't do any damage by doing so, your data will be unharmed and everything will continue to work in Jira, no crashes or errors will happen. But if your project admins amend the board, the workflow is automatically updated by that,…
-
If you have changed the format of the fields to the wiki renderer, then you should see the editing options on the fields when you are in edit mode. Are you seeing these?
-
No, as I said, it's 6.4 to 7.0 to 7.2, and yes you need to upgrade Confluence. All the versions on the download list are stable, so I'd simply go for the latest one.
-
You should upgrade Jira to 6.4, then 7.0 then 7.2 - see https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html I am not sure what you mean by "sync" - you'll need to explain that. But I suspect you mean link them together so they can exchange some information such as issue reports.…
-
Use the table of contents macro. It does it automatically.