Recent Changes - Search:

Cookbook

PmWiki

pmwiki.org

Cookbook /

JITS-Talk

Summary:
Version:
Prerequisites:
Status:
Maintainer:
Categories:

Questions answered by this recipe

Description

Enter your recipe's description here.
Testers wanted. Please try the JITS recipe and provide feedback. Debugging info appreciated

AuthUser usage

There are 2 pages only requiring AuthUser
- JITS/JITSsnip
- JITS/JITSadmin

and following expressions (#)

  • (:if auth admin :)
  • (:if auth edit:)
  • {$AuthId}

If any other authentication recipe enables a correct evaluation of these expressions then AuthUser is not necessary.

List of some authentication recipes

  • AuthPhpBB2 ... ?
  • MemberMgmt ... ZAP's member authentication system complies fully with AuthUser and will work exactly as expected in the expressions you use in JITS.
  • UserAuth ... ?
  • UserAuth2 ... ?

The above markup (#) is correctly evaluated by UserAuth2 and by UserAuth (since it is channelled through pmwiki CondAuth function which distributes to the different authentication modules). The page variable {$AuthId} is correctly set (to the authenticated user name) by UserAuth2 at least. ThomasP May 20, 2007, at 07:45 AM

Troubleshooting

  • check installed versions at your site on JITS/JITSsnip page
  • check local/config.php if <ZAP sources>.php and authuser.php included
  • check the <Group>.GroupAttributes?action=attr if ZAP password and READ restriction enables you to submit and read the pages
  • when JITS has been installed and a training group and pages created, test them before doing any customization.
  • if the issue is submitted but there is an empty pagelist
    • check the wiki.d/ folder too se if the issue file was really created.
    • If not, check the ZAP password, Site.AuthUser and current credentials.
    • Check how you are logged in - put somewhere (e.g., Wikisandbox) a line like I am [={$AuthId}=]

Customization

See JITS-Talk-Tutorial#Custom

Notes

Release Notes

If the recipe has multiple releases, then release notes can be placed here. Note that it's often easier for people to work with "release dates" instead of "version numbers".

Comments

Jiri, I installed the latest version. Clicking 'new issue' will give me the correct 'new issue' form, but after submitting it, it doesn't get saved. No new pages are created in wiki.d. Zap password for the group is set. Anything I can do to debug more?

Jiri February 09, 2007, at 09:05 AM What are the versions ? (goto JITS/JITS page in your site and check them)
It was tested with 

 PmWiki    pmwiki-2.2.0-beta25
 ZAP       Jan 14, 2007
 ZAPfiles  Jan 14, 2007
 ZAPplus   Jan 15, 2007

...(snip) ... As for "the page is not listed" - was the page really created? (make a standart pagelist and check it). You have to set in Group attributes ZAP password (maybe @nopass will do). The ZAP works such a way it says no message if unauthorized person submits the form. ...(snip) ...

  • hfwang February 11
    Jiri, it turns out that setting the ZAP password to '@nopass' made it work. Strange for I had set it, but it looks like _ONLY_ '@nopass' will work. I did included UserAuth, but not using it for anything else. It works now, Thanks!
  • Jiri February 11, 2007, at 05:42 AM
    It's good to know it works with UserAuth too. There are some differences between AuthUser and UserAuth and I preffered AuthUser as it is in thoe PmWiki core. The authorization is necessary only because of ZAP password and because the snippets use the {$AuthId} not to annoy the contributor with entering his name.
  • February 20, 2007, 12:53pm

Jiri, I have JITS running on a test wiki. Very neat. My question -- can you have JITS set to run on a PmWiki farm? If yes, can you give us a little guidance on what would be the proper settings for the $FarmD/local files, etc?

Thanks.

-- John McGinnis

  • Jiri February 17, 2007, at 01:46 PM
    John, I am terribly sorry I have no experience with PmWiki farms. I started experimenting with farms a year ago and after starting failure I had not time enough to follow all the things with linking pages and authorizations etc. Try yourself and if you have success share the knowledge here, please.
    Jiri
  • March 27, 2007, 1:16pm

Jiri, I have installed JITS and just love it!, It has made the Issue tracking a painless task. One Question: Would it be possible to add a edit link to comments. I have put in some comments and noticed some mistakes, and I cant edit them again to change them. (Unless I look in the wiki.d for the filename)

Another thing that is a bit of a pain, is when you edit an issue, say you just want to edit the comment, the fields Priority and Status reset to low and open (or the first selections in the lists) Can this be set as the current setting rather than have to change it each time we edit?

  • I didn't meet this. The initial value of the selectbox is given by the first "input select" option which value is set by current PTV already stored in the issue page. Have a look into JITS.JITScfgS snippet
    What version of PmWiki are you running? Jiri

Thanks for the great work!

-- Dean Staub

  • Sure, I will do it A.S.A.P. Jiri March 27, 2007, at 01:25 AM. Done in ver 20070327

Much Appreciated!

I think moving documentation to another page, and leaving this for talk/ideas is a good... idea. --OtherMichael
  • May 2, 2007, 10:18AM

I have a problem with including snippets. This is shown on ./MyJITS; 

IssueTracker /
JITS Standard pagelists

Login please 

----

version
20070418 
This page is not intended to be displayed. Contains snippets only. 

Filters and Issue pagelist 

[[#filters]]
*lots and lots of code*

I've checked and re-checked I have the right strings in the GroupFooter. Is this a problem with PmWiki? vers pmwiki-2.2.0-beta44

mbenfall?

  • Strange. OtherMichael had a similar problem. I think he fixed it by removing the space characters between <pagename> and #anchor in the (:include...:) commands e.g. 
 from (:include JITS.JITSsnip #grpftr#grpftrend:) 
 to   (:include JITS.JITSsnip#grpftr#grpftrend:)

Jiri May 02, 2007, at 04:34 AM

That worked for the main body of the page, which demonstrated the same problem, but has no effect on the footer. mbenfall? May 3, 2007, 8:45AM

  • OK, probably we know the cause. I will ask Pm in the mail-list why is the behaviour different.

In next version I will remove the spaces in all (:include commands in JITS.JITS* pages.
Jiri May 03, 2007, at 07:15 AM
Ops, not only this but 

 (:include <Group1>.<Page1> <Group2>.<Page2>#<a1>#<a2>:)

must be changed to 

 (:include <Group1>.<Page1>#<a1>#<a2> <Group2>.<Page2>#<a1>#<a2>:)

Will be fixed ASAP. Jiri May 03, 2007, at 10:19 AM
Fixed in ver. 20070503 - Please test it. Jiri May 03, 2007, at 10:33 AM

  • Works perfectly. Thanks so much! mbenfall? May 8, 2007 10:48 AM
  • July 17, 2007, 07:58AM

Hi, I am testing PmWiki + JITS for my company. It looks very promising. Is there a way to integrate email in JITS when new issues are submitted, or when new comments are added, or with any other status changes? Or would I use PmWiki.Notify? I also noticed that the ZAP module ZAPmail is deprecated.

Basically I would like to be notified by email of any new issues and changes.

  • pmwiki-2.2.0-beta57
  • JITS 20070515
  • ZAP: May 31, 2007
  • ZAPtoolbox: May 31, 2007

Thanks! psp_kevin

  • I use PmWiki.Notify. But it notifies even when filters or sorting is changed. Depends how you create the notify statements (I did no experiments). Jiri
  • September 9, 2007

Hi; first of all - great job! I love it :) And it beautifully shows that PmWiki pagelists + page-variables make a deadly combo when used with ZAP........ :)

One thing quite important to get corrected ASAP: the number for newly created issue-pages ("#" in ZAP) should be generated when they are saved, not opened. I think it can be done somehow using zapsubmit. Otherwise the issues may be going to magically disappear if someone creates new issue before someone else closed his one. And I think that already happened to me :) Or am I totally wrong?

As a side note, I'm currently working on adding some versions related fields to JITS, aiming for a pretty RoadMap with cute progress-bars along with auto-generated ChangeLog. The other feature I'd like to add would be a field "Assigned to: <user>", but I don't really need it yet, so it'll have to wait :) I'll try to share after some more testing.

Greetz, MateuszCzaplinski

Sept. 12, 2007 3:09 PM EST I installed your great tool and pushed it out to our group to begin using. We posted 38 issues and suddenly they all disappeared. We cannot even add new ones. Nothing shows up except the new issue button and the sort form. We haven't made any changes to any pages or files. I looked in the wiki.d directory on the server and I see the files that were generated so they aren't lost but I have no idea why we can't see them now. Ideas?

Thanks, Sleahcim

Sept. 12, 2007 5:51 PM EST After a few more tests I was able to get the list back but when someone else looked at the same issues tracking page on another computer with a different login the list disappeared again. I set up a separate issues tracking page under a different group, added a few issues, repeated the above scenario (page open on two computers with two different logins) and the list disappeared again. I have ZAP pass set at @nopass for the Group so I don't understand why this would be happening. This appears to be a bug. Any suggestions?

Sleahcim

Has anyone tried it recently, in the latest stable release? I am not able to get it to work properly. By default when I go to the main MyJITS page it does not display the table but displays the raw markup instead.

farhad May 10, 2009, at 10:56 AM

Is there still a source for ZAP and ZAPToolbox? The link in the main page no longer works. Link gets a 401 - can't find host.

tamouse June 04, 2010, at 03:34 PM

I placed a link to the source in my site http://www.revida.sk/wiki/index.php/Test/JitTests

Just copy the text files and rename to .php

Jiri

See Also

Contributors

Talk page for the JITS recipe (users?).

Edit - History - Print - Recent Changes - Search
Page last modified on September 10, 2011, at 11:42 AM