Trac-admin should permit issue or task creation

[philippe@…]

Hello,

I saw trac-admin allows to close an issue. I suppose this is dedicated to let user create SVN hooks for example.

In the same way, I'd like to be able to open an issue or a task from CLI. Indeed, it would be a great way to automate ticket opening.

It would be interesting to open a task from crontab or to create a function in our programs to relay some stderr to trac-admin in order to open an issue.

Concerning tasks, I suppose everybody could be concerned. Concerning issues, I know that most projects do not need this because tickets are bugs detected by users but in other organizations, people worked this way (particular error need to be solved via a ticket or particular jobs take an inventory of possible errors in a ticket). I personally would be really interested to open an issue if a program do not execute the "if" but the "else" :)

Regards, Phil.

[Remy Blank]

There's already a way to create a ticket programmatically: using the ​th:XmlRpcPlugin. A trac-admin command providing the same functionality could easily be implemented in a plugin, by implementing the IAdminCommandProvider interface. But I don't see the use as being high enough to warrant adding this to Trac core.

Voting to close as "doinaplugin".

[anonymous]

According to this article: ​http://trac-hacks.org/wiki/XmlRpcPlugin, the plugin doesn't seem to be actively maintained.

Moreover, I think this should be permitted by CLI as creation of milestone is (among others).

Regards, Phil.

[Remy Blank]

Replying to anonymous:

According to this article: ​http://trac-hacks.org/wiki/XmlRpcPlugin, the plugin doesn't seem to be actively maintained.

What gives you that impression? The last commit was on 2011-02-04, and the current maintainer (osimons) is also a Trac developer. The "(not actively maintained)" comment at the top mentions the plugin version for Trac 0.10 only.

Moreover, I think this should be permitted by CLI as creation of milestone is (among others).

I'm sure that's of use to some people, just not enough to warrant inclusion into Trac core. Especially if the required interfaces to implement it as a plugin are already available.

[AdrianFritz <adrian@…>]

Replying to anonymous:

According to this article: ​http://trac-hacks.org/wiki/XmlRpcPlugin, the plugin doesn't seem to be actively maintained.

It is maintained (last commit by 2011-02-04 for 0.11 / 0.12) The version it's not maintained is 0.10

[anonymous]

My apologies ! The comment in top of the article I mentioned let me think it was not. You convinced me on that point (the plugin).

Concerning the adding of this enhancement to trac-admin: I am sure it would be a great feature but I have to let you decide.

Regards, Phil.

[anonymous]

Replying to rblank:

I'm sure that's of use to some people, just not enough to warrant inclusion into Trac core. Especially if the required interfaces to implement it as a plugin are already available.

Just to add an argument: I know at least one company who cares about this kind of feature since they use a huge team of people to tidy logs in order to open tickets to specialized teams. In this kind of organization (Level 1 to monitor machines and logs, level 2 to know the business of a particular part and level 3 to know the application who do the business of this part), automatizing this operation would be interesting (for level 1). I'm quite sure this organization is not a lonely one so it may represent enough people to warrant inclusion into Trac core.

Of course, we are not speaking here about the traditional model of a free software who doesn't need to work like this. And I think trac is mostly used by people who are in this model. But that doesn't mean it is not a major way to work, in other structures.

I will stop here to defend my opinion ;) I let you decide if this ticket must stay opened or not. Thank you to debate about it!

Regards, Phil.

[Ryan J Ollos <ryano@…>]

Replying to rblank:

There's already a way to create a ticket programmatically: using the ​th:XmlRpcPlugin. A trac-admin command providing the same functionality could easily be implemented in a plugin, by implementing the IAdminCommandProvider interface. But I don't see the use as being high enough to warrant adding this to Trac core.

In the past I have searched in the documentation for a ticket add and was surprised to not find it. I think a good argument for adding the command is that it is a very basic operation that most people would probably expect to be part of TracAdmin, and it would make the basic command set more complete. An argument against it is that it could get very complicated quickly. How much info would you allow to be set via the command interface? Would you allow adding a description, summary, comments; setting the milestone, version, priority, …?

An alternative to ticket add would be ticket import. Since we have wiki import, I'd expect to have ticket import as well. Of course, you'd probably need a ticket export command first! But once you have a ticket import command, you'd have a way to create tickets from the command line with trac-admin (i.e. I'd assume the creation of the ticket could be scripted and then you could import it).

From a user standpoint, I'd be in favor of having the ticket import and ticket export commands added to trac-admin.

[Christian Boos]

We already closed a similar ticket as wontfix (#8998), but I think that at some point in the future point, ticket import/export will certainly be a natural operation to support (#8383), so I think we should keep this on the radar.

[Carsten Klein <carsten.klein@…>]

I would propose outsourcing this to tho.

Over at tho. create a project that will provide admin commands and admin command providers doing exactly what these peops want, reusing the XmlRpcPlugin.

No need to make this a part of the "core" IMO.

That way, the community could provide additional admin commands for automation purposes…

[Ryan J Ollos <ryano@…>]

Related: trac-admin ticket import / export is requested in #10699.