Comments
-
It sounds like you are on an older version of JIRA that does not yet have the "transition issues" permission. What version are you on?
-
Not in later versions of JIRA
-
Off the shelf, an internal username/password prompt. It then supports LDAP and Crowd lookups natively with minor config tweaks. (Technically, the username/password is Crowd as well, but it's internal) There are plugins that provide more clever stuff and an API to allow you to write your own. This is kind of a vague…
-
Confluence provides many spaces. It's very easy to set up some spaces as generalised wiki spaces, others as knowledge bases, others as project spaces and so-on. You just install Confluence once on one server.
-
That looks fine to me, with two caveats. You have already mentioned both things I'd question though! First, I'd probably revise the transitions slightly - think of the status as a "useful name for the current state of an issue" and the transition labels as "an action to do to move from one state to another" - many…
-
I am afraid there's not enough information in the question. I can see you are working on a board, but I don't understand "draft a sub task in progress". I can guess that "the assigner changed" means a field was changed, but which field, and how? And what are we trying to fix?
-
It's from the Jira suite utilities.
-
I'm afraid you have not understood what I've said. Your example even proves what I'm saying - it's not usefully searchable, it's arbitrary, and it's as clear as mud to most users. If the boilerplate information is for the managers, then the worst possible thing you can do is put it something the users can edit. You…
-
Mmm, I'm still thinking that if you have users who are really well behaved and always remember to edit the comment before posting it, then you've got users who don't need prompting or boilerplate. I really do understand your point about "we need to find comments related to a transition". It's a bit clunky, but it does make…
-
You've still got the very human point that if you fill in a default, your users are simply not going to bother. In which case, the data is redundent - you know what they're going to enter because they're using transition X. Your use-case does make sense, but I think you're over-engineering it, and a single filed with…
-
What's wrong with a "reason for latest rejection" field?
-
I did it with javascript hacks, but in version 4. I removed it after we realised 99% of the comments were set to the default because the users ignore it. I'd strongly recommend not wasting your time doing this. Only make a comment if you have something useful to say, the users will just let junk drif in if you default it.
-
Not quite. It's the same data you are hitting, so the permissions and issue security are identical on all nodes.Note that your plan to have internal and external facing systems won't work properly either - JIRA needs to be run on one single url, it can't have two.
-
Nope. JIRA requires full read/write access to its database. It won't even start without it (for safety). So you'd have to have the slave enabled for write access. Then your second JIRA would stomp all sorts of damage over your production data. It's fine to replicate the data, report off it, read it, use it to create the…
-
I've done it with the script runner(That's how I found out users don't like it because the diagrams become useless to them)
-
No. You either use "all" or you use the transitions you actually need. Now, there is a workaround - you can find/write an addon that provides a Condition of "current status in (x, y, z)", and that can make a shared transition vanish in certain cases. Be very careful before you do it - your users rely on the diagram and…
-
I'm not sure how you'd do that - squashing commits in git does make sense, but if you did it in Jira, you'd be effectively destroying information that is the whole point of having a history.
-
I've run into problems with around 300-ish change groups (by change group, I mean each entry of "person X changed this issue" - it didn't seem to matter if the changes were one field, or several). If you do amend your processes to avoid writing the history lots, then some ideas: 1. Think carefully about comments - I've run…
-
No. The history is there to show you the changes made to the issues. The Jelly script changes the issue so it's a nonesense to hide it. You would need to amend the core code of the workflow functionality to prevent it writing the history, and then you'll end up with an inconsistent history and users saying "this issue is…
-
Best option is to use "find new add-ons" in the add-on management section of Confluence in the admin section
-
The one that springs to mind is the Adaptavist "content formatting" ones - they contain things like lozenge macros that can help you colour and reformat text. But that could be a bit of an advert, as I work for them. You'll have to take my word for it that I'd have said the same even if I didn't work there. (Even though…
-
I'd agree with Milo on this - there's nothing free that would do this easily, and most users would reach for Gliffy or Lucidchart to do it. It should also be possible with the Graphviz or UML add-ons, but again, paid options. If you've got some of the free formatting add-ons for Confluence, you could probably build…
-
Yes. You can have a very large list of users in JIRA's user database. The applications consult their licences separately and simply count up people in the group(s) that are allowed access. A JIRA with a 25 seat licence doesn't care if you have say 500 users, and you put 99 of them into confluence-users (so that they can…
-
Ok, a null what? You'll need to give us more information if you want our help.
-
Possibly damaged data in the database. We'll need more information really.
-
That's a huge essay question. I'd suggest you type "testing" into google and read everything.
-
My suggestion will either fix it, or give us more information on what's going wrong :-) Obviously, I'm hoping for the former...
-
Ok, apologies, I didn't see the first reply. Your "browse" line looks correct to me because it "group: Kimbia". That means anyone in that group should be able to see all the issues in the project That is separate from the right to log in. You need to make sure your Kimbia users are also in at least one group in the "Jira…
-
But the "browse" line you posted has nothing against it. Could you tell us what it actually says? Also, what do you have under Adminstration -> global permissions for "Jira Adminstrators", "Jira System Administrators" and "Jira users"?
-
Well, that explains it - you haven't allowed anyone to browse the project.