I wonder if it's possible to specify ticket "types" in Jira and have specific data that MUST be filed in for a given ticket type. Say we have a "campaign start" ticket type. In that the creator must set a few dates, attach a file with some data etc. And also have a default cost in time for a given ticket type so that an estimated date when it could be started and done could be shown. Is this possible?
Edit: By And also have a default cost in time for a given ticket type so that an estimated date when it could be started and done could be shown. I mean if it would be possible to set that a 'campaign start' type of standard ticket would require 3 days of work to get done. So that if we let a specific few people create tickets they could see like a time-line of when their ticket could be started on and when it could be assumed to be completed.
Yes - there is quite a bit possible with JIRA, including enforcing fields at certain stages and so on / so forth. This is all well documented on the Atlassian site, or you can work with one of their partners (like us :-) ...) for setting up your project configuration.
Enforcing certain fields can be done through the field configuration scheme or through the use of specific plugins.
Could you elaborate on
And also have a default cost in time
for a given ticket type so that an
estimated date when it could be
started and done could be shown. Is
this possible?"
Francis
The specific documentation is on Field Configuration Schemes. The default cost in time sounds like setting a default value for the system Original Estimate field, which it would be nice if you could also do via the Field Configuration Scheme, but you currently can't. I'd look at some injected javascript to set a default, perhaps using the Behaviours plugin.
Related
I'd like to perform operations like automatically update a field based on another field's value (for example if the assignee field is empty automatically assign to a default, set an hidden "due date" field based on the release-fix start date, ecc.) or write a custom validator that does validations based on a combination of values.
Every time I go searching on the jira forum I find java fragments of code, so everything seems to be possible, but it seems it is only at one condition: to buy the script runner plugin!
It seems strange to me: of course this plugin seems to be doing a lot of boilerplate for you but...what if I want to make a little more effort but still not payng for something that, in my opinion, should be free? I'm already paying the software license...isn't there another way to perform such post actions?
Try MyGroovy. It provides similar features. For tasks like execution post-functions I suppose it would fits good.
This question may seems odd but we have a slight mixup within our Report Suites on Omniture (SiteCatalyst). Multiple Report Suites are generating analytics and it's hard for us to find which site URL is constituting the results.
Hence my question is, is there any way we can find which Site is filling data within a certain Report Suite.
Through this following JS, I am able to find which "report suite" is being used by a certain site though:-
javascript:void(window.open("","dp_debugger","width=600,height=600,location=0,menubar=0,status=1,toolbar=0,resizable=1,scrollbars=1").document.write("<script language=\"JavaScript\" id=dbg src=\"https://www.adobetag.com/d1/digitalpulsedebugger/live/DPD.js\"></"+"script>"));
But I am hoping to find the other way around that where Report Suite gets its data from within the SiteCatalyst admin.
Any assistance?
Thanks
Adobe Analytics (formerly SiteCatalyst) does not have anything native or built in to globally look at all data coming to see which page/site is sending data to which report suite. However, you can contact Adobe ClientCare and request raw hit logs for a date range, and you can parse those logs yourself, if you really want.
Alternatively, if you have Data Warehouse access, you can export urls and domains from there for a given date range. You can only select one report suite at a time but that's also better than nothing, if you really need the historical data now.
Another alternative is if your sites are NOT currently setting s.pageName, then you may be in some measure of luck for your historical data. The pages report is popped from s.pageName value. If you do not set that variable, it will default to the URL of the web page that made the request. So, at a minimum you will be able to see your URLs in that report right now, so that should help you out. And if you define "site" as equivalent of "domain" (location.hostname) you can also setup a classification level for pages for domain and then use the Classification Rule Builder and a regular expression to pop the classification with the domain, which will give you some aggregated numbers.
Some suggestions moving forward...
I good strategy moving forward is to have all of your sites report to a global report suite. Then, you can have each site also send data to a site level report suite (warning: make sure you have enough server calls in your contract to cover this, since AA does not have unlimited server calls). Alternatively, you can stick with one global report suite and setup segments for each site. Another alternative is to create a rollup report suite to have all data from your other report suites to also go to. Rollup report suites do not have as many features as standard report suites, but for basic things such as pages, page views, it works.
The overall point though is that one way or the other, you should have all of your data go into one report suite as the first step.
Then, you should also assign a few custom variables to be output on the pages of all your sites. These are the 4 main things I always try to include in an implementation to make it easier to find out which sites/pages are reporting to what.
A custom variable to identify the site. Some people use s.server for this. However, you may also want to pop a prop or eVar with the value as well, depending on how you'd like to be able to break data down. The big question here is: How do you define "site" ? I have seen it defined many different ways.
If you do NOT define "site" as domain (e.g. location.hostname) then I suggest you pop a prop and eVar with the domain, because AA does not have a native report for this. But if you do, then you can skip this, since it's same thing as point #1
A custom prop and eVar with the report suites(s). Unless you have a super old version of legacy code, just set it with s.sa(). This will ensure you get the final report suite(s), in case you happen to use a version that uses Dynamic Account variables (e.g. s.dynamicAccountList).
If you set s.pageName with a custom value, then I suggest you pop a prop and eVar with the URL. Tip: to save on request url length to AA, you can use dynamic variable syntax to copy the g parameter already in a given AA request. For example (assuming you don't have code that changes the dynamic variable prefix): s.prop1='D=g'; Or, you can pop this with a processing rule if you have the access.
you can normally find this sort of information in the Site Content-> Servers report. There will be information in there the indicates what sites are sending in the hits. Your milage may vary based on the actual tagging implementation, it is not common for anyone to explicitly set the server, so the implicit value is the domain the hit is coming in from.
Thanks C.
I'm wondering how to assign two users to one task in JIRA. I took over a project that was set up by someone else. The problem is we are doing pair programming and we would like to keep track of time.
I dont think you can not actually assign two users to field assignee as it is built-in field.
You can create new required field e.g. pair-assignee and have pair tracked there. Here is a doc about how to setup a custom field.
By design, this is not possible as such - it's a single value field.
But there are ways around this limitation.
Since a number of people had this question, Atlassian has set up a page for the possible solutions/workarounds.
I'm trying to use JQL to measure cycle times (the Control Chart has other issues), so I need to get the date that an issue changed status. I see that one can use the CHANGED keyword to filter issues that have changed status on certain dates, but I see no way to actually list the date of the change as a column.
Any ideas? How would you guys address this lack of visibility into cycle time data?
There is no simple solution available in JIRA at the moment. See the issue https://jira.atlassian.com/browse/JRA-12825 for the whole discussion. The argumentation of Atlassian is the following:
There exists a product Service Desk that implements the SLA feature expressed here.
There are reports and additional plugins available that give similar information to this. See the JIRA Suite Utilities which give you a UI for each issue to see the transition summary.
JQL (JIRA Query Language) was intended to select all issues that match a query, not to select special information to these issues. You have to use the configuration of the table, if it is included there as a field of the issue (which it is not).
In addition to the suggestions from mliebelt there is another at https://answers.atlassian.com/questions/128370/how-to-capture-date-of-state-change-in-jira. It requires JIRA Misc Workflow Extenstions and uses the "Copy value from field to field" function to capture the transition date in a custom field.
There is a plugin in Atlassian Marketplace called Time in Status just for that purpose. The plugin prepares a report on how much time each issue spent on each status or assignee.
Time in status is useless if need to count of Jiras that changed status on that day. Time in status widgets is useless for this
I would like to customize a Work Item Type in TFS to automatically set the Assignee to a particular role. For example (to compare to another Issue Tracker), in JIRA the default Assignee is the Project Lead (so that any ticket not otherwise assigned, gets automatically assigned to whatever person is designated in the role of Project Lead). Can I do something similar in TFS?
So, I realize that one difference between JIRA and TFS is that TFS doesn't (to my knowledge) have the concept of "Roles". The closest thing to that is "Groups", but unlike Roles, Groups can have multiple people (which may be the restricting factor in this problem). I know how to configure a TFS Work Item so that only a certain Group gets listed in the "Assign To" field, but I would like to go a step farther, if possible, and create a custom Group with just one member (e.g., "Issue Guru") and then set up the work item to get automatically assigned to that person.
I'm trying to replicate the Jira functionality here, and maybe there is just no good way to do it in the TFS framework. Any suggestions?
There's a Step by Step Guide on Ivan Fioravanti's Blog for enabling it.
If you are unfamiliar with customising Work Item Types, have a look at the following links (stolen from Grant Holliday's blog).
I never tried this in production but here is something I tried quickly and it seems like it could work.
You can set the default value to a Group by editing work item template in template editor.
Just select Assigned to field and add a DEFAULT rule like shown in the image below.
This will also require you to create one or more groups (one global or maybe one per project). Once you set this up you won’t have to make any updates in the future but only manage people who are in the groups.