Opened 14 years ago
Closed 14 years ago
#1542 closed enhancement (fixed)
Plug-ins should be able to suggest a better job name
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | BASE 2.17 |
Component: | core | Version: | |
Keywords: | Cc: |
Description
When creating a new job a default name is generated based on the name of the plug-in, eg. Run plugin: name-of-plugin
. This is usually not very informative. It would be nice to let the plug-in suggest a name for the job. For example, the reporter importer could generate something like this: Import reporters from foo.txt
.
This should not be too hard to implement. We can, for example, add Response.setSuggestedJobName()
to the response object that the plug-in can call at the end of the configuration sequence.
If the plug-in doesn't suggest a name, the existing default should be used.
Change History (3)
comment:1 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 14 years ago
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [5480]) References #1542: Plug-ins should be able to suggest a better job name
Fixed in the core API. Plug-ins can now call
Response.setSuggestedJobName()
to suggest a job name. The reporter importer was used as a test case. I will fix this in the remaining core plug-ins.