Comments
-
Now Asterix or Tintin, I'd be up in the 95% range
-
6. Lorax!
-
I could do with a good solid RSS feed for Jira release notes too!
-
The security page has a FAQ at https://www.atlassian.com/trust/faq I found a vulnerability in one of your products, how do I report it? If you discovered a vulnerability in one of our products, we appreciate if you let us know so we can get it fixed ASAP. Have a read through our instructions for how to report it and you…
-
Yup. These days inserting data directly into a database of any complexity is like patching a binary executable. While it's running.
-
It worked for a few years ago just setting the property on all the statuses
-
Rename them with a prefix, e.g. zzz DO NOT USE original component name It's ugly but works
-
Why are workflow schemes hard to change? Active workflow names yes, I agree.
-
You can also move the one issue to a new project/issuetype that uses a different workflow. Then change it back to the original project and workflow. Annoying!
-
Also tracked as https://jira.atlassian.com/browse/JRASERVER-64106
-
Good write-up!
-
Well, they are separate products now, Cloud and Server
-
I'd say it's how Jira does autoassignment of issues. And you can have multiple values for the Components field. And it's complex how that affects autoassignment!
-
BTW, I'm the lead Jira admin at LinkedIn. Before this I've consulted about Atlassian tools for about 150 companies over 11 years. And I've been using Jira since 2.x. So I've heard similar frustrations before. And if a simpler tool really works for all what you want, then that's ok - use it.
-
I'm happy enough. I still want more from the product, but I feel that for what it does, and for the price, there's not much to match it. That said, it sounds like using Jira Cloud might make things easier for you? No system admin needed. There are still many ways to configure and mis-configure Jira, I know. But that's true…
-
Phew!
-
That's handy!
-
In the database, select * from clusternode Not sure why it isn't shown in the UI in Jira 7.2
-
A user can be a member of multiple groups. You could use the JQL such as reporter in membersOf("mygroupname") https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-functions-reference-764478342.html#Advancedsearching-functionsreference-membersOfmembersOf()
-
The status changes should make it clearer to everyone what is the level of engagement for each issue in j.a.c. I don't think they are intended to change how Atlassian decides what work on.
-
Here's how that plugin calculates the score: https://confluence.everit.biz/display/FSDL/Score+calculation+and+ranking But it's not clear that Atlassian is going to publish the exact algorithm for UIS. Because then we would game the metric :)
-
From the linked j.a.c. issue I see "JIRA does not employ methodology which would enable exploitation of these old vulnerabilities(detailed in CVE-2017-15095" It doesn't sound like the "serious vulnerabilities" are happening. So I'd expect this is a lower priority to fix
-
You can store the name of the previous status. Then define a transition from Needs More Info to each of the possible previous states. Use a condition to only show one of these transitions based on the value in the custom field Previous Status. That way only one transition will be see and it will go back to the correct…
-
I think Unassigned just means that the Assignee is null underneath the covers. No such user as "Unassigned" in the cwd_user table. So clearing the Assignee should make the Unassigned user reappear, if it is globally enabled
-
Or use ScriptRunner to access the workflow Java object and go from there
-
See https://developer.atlassian.com/server/jira/platform/java-apis/ "For example, a method that is marked as deprecated in JIRA 6.1 will still work in JIRA 6.2, but will be deleted in JIRA 7.0"
-
Yes, but why would a deprecated APi be removed in a patch release? I thought the API was stable until release versions?
-
Admins always like guidance about "what use is this feature?" beyond "what does this button do?" And also, what should I not do, and how can I help Jira and Confluence scale
-
Ah, I see that agility projects are a newer feature https://confluence.atlassian.com/get-started-with-jira-software/three-common-jira-software-boards-937185142.html (off to work out how to disable that for our 10000 users and our next upgrade)
-
And schwag is useful!