Comments
-
You might want to try the "integrity checker". In hard stops of Jira, or crashes, or certain broken plugins, it is possible for Jira to get confused about workflow states. The symptoms are what you're seeing - despite having perfectly valid transitions out of a status, even with no conditions on them (so anyone can perform…
-
See https://www.atlassian.com/software/jira/pricing/ All server licences are initially a year, with annual renewal. For Cloud, you pay monthly, but once you have an account, that can be altered.
-
That would explain it - the type of event determines the subject line (generic event comes out as "issue updated") and who it goes to in the notification scheme. Try changing the event from "generic" to "Issue reopened", then it should behave as you expect.
-
Ok, go into the workflow and look at the "Reopen" transition - specifically, the one in your screenshot, with the id of 731. Look at it's post functions and look for the "fire event" one - what event is it firing?
-
Ok, then you'll need to do some deep debugging. * Get an issue ready to be moved through the transition. Then go to * Administration -> System -> Logging & Profiling -> Click Edit next to the com.atlassian package and set the level to "debug" * Commit the transition, with only a comment, so that you get the "no email sent"…
-
Hmm. That does not sound right at all. The event on the end of the transition should always trigger an email, it should be irrelevant whether the user is filling in data or not. Do you have any listeners or email related plugins that might be doing something different to aff-the-shelf Jira?
-
Check the event on the transition, and what the ntoification scheme does for that event very carefully. Make sure the notification scheme is set correctly on the project. Is it possible another admin has changed it (or even yourself by accident - I'm my own worst enemy when it comes to forgetting what I've been updating)…
-
Er, find an account that is an admin, and use it If you're referring to JIRA Cloud, then you can't. You will not get access to the system admin, it's restricted to Cloud support people only.
-
From what you've said, the images should appear, so it's not a case of doing something differently to display them, more a case of making the systems do what they should be doing. I think you need to look for patterns: Is it consistent? I mean, can you always guarantee that one set of images will appear, and another set…
-
I'd use the Jira database values plugin, and point it at the "project" table inside the same Jira. See https://marketplace.atlassian.com/plugins/org.deblauwe.jira.plugin.database-values-plugin
-
Are you using OnDemand Jira? If you are using your own installation, then you need to ask someone already in that role. If they have all left or are unavailable then see https://confluence.atlassian.com/display/JIRA/Retrieving+the+JIRA+Administratoras a last resort. If you are using OnDemand, then no. You won't get…
-
You can't - the option is all-or-nothing. You can either use links (add and delete) or you can not use links at all. There's no difference between "add" or "delete", they're bundled together as "use links"
-
That's what a mysqldump file is for - recreating a database. I'd install a clean Confluence 5.1 hooked up to an empty database to start with, just so that you know it works without data, and you don't have to manually deal with any config. Then stop it, and edit the dbconfig.xml file in the confluence-home directory so…
-
There's a lot wrong with that... * A mysqldump is a block of text you can use for recreating a database. It's in no fit state to be merged with any other database, it's for creating copies of a database. It'll trash the database it's restored into * You should never never never write to a running Confluence with SQL *…
-
Yes.
-
Yes.
-
Ok, you definitely want a "condition" then, as a user won't be offered work logging in a transition screen, so a validator would be annoying.
-
I think you'll need a script or a bit of plugin code to provide this, but you could either create a "condition" (that would hide the transitions on any issue where there are no hours), or a "validator" (would return the user back to the transition screen if they try to proceed without any data in the field) I suspect the…
-
You will need to hack the core code in JRA so that it stops allowing it. Although you say "only admin or non-admin user can", which works out as "all users". The current system only allows project admins to do it.
-
You'll need to do a spot of coding to catch that event and send an email, but it will be too late - the version will have been deleted, you can't stop them doing it.
-
Nope, you can't hide them either. The answer is to remove ALL rights to maintain versions, or, exactly as Jobin says, work with the user, instead of trying to force them down a route they don't like. Why is he deleting versions? Why do you need to keep them if he, as a project admin, decides he doesn't want them? Sounds…
-
You can't. If they are a project admin, then they have the right to maintain versions - add, change and delete.
-
There's not a lot we can tell you - you haven't defined the problem beyond "I can't access it", and the best answer to that is in the documentation.
-
For writing a Confluence add on, start at https://developer.atlassian.com/display/CONFDEV/Confluence+Developer+Documentation For the basics of using Jira's REST interface, I'd recommend a look through the tutorials - see https://developer.atlassian.com/display/JIRADEV/JIRA+REST+APIs
-
You need to add "fix version" too. Fix version and Affects version are separate fields, which use the same list of versions as options. (Don't worry about admin rights though - admin rights gives you admin. Not "access everything", you still need to make sure you have the resolve issue permission as a user. Even if it's…
-
Ok, two quick things1. You could try adding "affects versions" just to check the functionality (remove it after testing that it appears there if you don't want to use it)2. Check your permissions - do you have the right to *resolve* issues? If you don't, then you don't have the right to set a fix version, and Jira removes…
-
What does "it does not show" actually mean? On both issue and transition screens, do you mean it your new version does not show in the affects and/or fix version field drop downs? Or the fields do not appear at all? I am guessing that by "project screen", you mean the summary of the project. It won't show in there until…
-
No. JIRA does not track "view issue". It would be an utter nightmare for the end users - just wandering around doing my job results in hundreds or even thousands of effective "view" events during a normal day. It would be absurd to overload your server tracking them all, and your users would simply spam filter the lot. If…
-
No problem.You can make some versions of Confluence work with Openjdk, but it's not supported at all. Could you swap to using Oracle's Java? 1.7 or 1.8
-
Ah, well, that error is typical of using an incompatible version of Java.You have said you're on Confluence 5.7 - what version of java are you using? (The exact version, as I seem to remember that there are a couple of specific releases that cause problems)