Component Versions JIRA Plugin

Component Specific Vesions is a JIRA plugin that allows you to define which versions are valid for which versions, and enforce this during issue operations. For more information please visit

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)


ShopaHolic iPhone uygulaması ile Limango, Markafoni ve Trendyol kampanya sitelerindeki kampanyaları yakından takip edebilirsiniz. Tek bir arayüz üzerinden kampanyaları takip edip fiyat karşılaştırması yapabilirsiniz. İsterseniz anahtar kelimeler tanımlayıp uygulamanın size haber vermesini sağlayabilirsiniz. Kampanya’dan ürün sayfasına kadar ulaşabilir isterseniz “Satın Al” fonksiyonu ile ürünü ilgili sitenin kendi arayüzü üzerinden satın alabilirsiniz.


VN:F [1.9.22_1171]
Rating: 10.0/10 (2 votes cast)

Resolution and Status Colors JIRA Plugin


Resolution Colors Plugin enables issues to be shown with different color depending on their resolution and Status Colors. Why do you need this, aren’t just the Status Colors enough? Unfortunately, no. Because unlike most other issue management systems, a ‘Resolved’ status does not show that the issue is solved. An issue may be resolved because assignee may have decided not to implement it with specifying a “Won’t Fix”, “Cannot Reproduce” or “Incomplete” resolution. So while checking resolved issues, you have to pay special attention to the ‘Resolution’ field.

So what this plugin does is that; this plugin makes it easier to highlight issues according to their resolution type for issue reporters or verifiers. But if you want, you can use this plugin in a way that it only highlights issues based on their status.

Resolution Colors

Initial Configuration

After installing plugin you have to do some initial configuration to activate plugin’s features. The first thing you should do is adding a new custom field of type ‘Resolution Color’. Although the name of this field is ‘Resolution’ it can also highlight issues based on their Status.

  1. From issue administration page, scroll down to ‘Fields’ section and click on ‘Custom Fields’ link. List of your existing custom fields will be displayed. Select ‘Add Custom Field’ from top right of the page.

Resolution Colors

  1. A pop-up dialog box will be opened. Select ‘All’ and write ‘Resolution’ to search field. ‘Resolution with Color’ custom field type will be displayed as shown in the following figure. Select it and click ‘Next’.

Resolution Colors

  1. Enter a name for the new custom field. This name will be displayed as the column name in the issue list. You can enter any description you want, it won’t be displayed to end users. Finally click on ‘Create’ and your custom field will be created.

Resolution Colors

  1. You have to select, on which screens this custom field will be shown. You have to select every screen that contains resolution field, and you want issues to be colored according to their resolution.
    Resolution Colors
  2. Your custom field is now ready to use in issue detail pages. But you have to configure the issue list pages too.
    Resolution Colors
  3. Open the issue list and click on ‘Columns’ on top right of the page. Write ‘Resolution’ to the search field and two Resolution fields should be displayed. ‘Resolution’ is JIRA’s build in ‘Resolution’ field and ‘Resolution with Color’ is our new custom field. De-select ‘Resolution’ and select ‘Resolution with Color’ field and click on ‘Done’. If you change your systems default column layout, every user will start with that layout. But if they have already an active column layout they will need to add ‘Resolution with Color’ field to their column layout as well.

Resolution Colors

Note that, you can even add this column to your issue lists in dashboards to make them colored.

List Views

For issue list to be colored you have to add ‘Resolution Color’ custom field to the column list. Without it, there won’t be any coloring in issue list view. You may add this field to default list view columns so that it becomes active for all users by default.

Issue List View

You can also colorize issues in dashboard widgets by adding the same ‘Resolution with Color’ field to columns shown in the dashboard.
Coloring in Dashboard

Issue Detail View

Depending on plugin’s settings different parts of the issue details view are highlighted. Please see ‘Plugin Settings’ section.

Issue Details View

Plugin Settings

You can use the plugin without adjusting any settings. It comes with reasonable defaults. But if you want further customization, or your JIRA Status and Resolution fields are highly customized you may want to tune Plugin’s Settings. There are two settings page, one for ‘Resolution Colors’ and the other for ‘Status Colors’.

Resolution Colors

Plugin assigns its default colors to JIRA’s built in ‘Resolution’ options. If you have custom ‘Resolution’ options you may also assign colors to them. You can also change predefined colors for build in ‘Resolution’ options. Be careful while selecting a resolution color, each device (Projector, Printer, Screen) may display colors differently and this may cause issue details to be unreadable if you select a color that is close to black (normal text color), or blue (link color). So in general, avoid dark colors. For example if you want to use red try to select a very light red.

In addition to the color, you can also select which part of the issue detail view to be highlighted.

  • Header : All issue details fields are colored.
  • Resolution : Only the resolution field is colored.
  • None : Coloring is turned off.

Plugins Settings:Resolution Colors

Status Colors

If you need to differentiate issues based on their status you have to configure Status Colors too. The key is that Resolution Colors have priority over Status Colors. For resolved issues their Resolution Color is used. This is why there is no color setting for “Resolved” status in ‘Status Colors’ configuration page. There is a special case however, the plugin allows you to use ‘Status Color’ of Closed status instead of ‘Resolution Color’ if you set it from ‘Closed Status Coloring’ configuration option.

Closed Status Coloring

  • Use Status Color : For closed issues their Status Color is used instead of Resolution Color.
  • Resolution Color : For closed issues their Resolution Color is used.

Plugin Settings:StatusColors

If you want to use this plugin to highlight issues based only on their status field, you can. You have to specify the same color to every Resolution option and assign different colors to Status options.


VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)

Similar Issues JIRA Plugin


Similar Issues Finder Plugin targets to minimize number of duplicate issues within JIRA. Each duplicate issue takes precious time of its reporter, assignee, management and QA teams without any significant benefit to the end product. For a 500 employee organization saving 1 minute of each person a day will save nearly 3 months each year. Even a single duplicate issue may easily cause an hours work.

Similar Issues Plugin

Similar Issues Overlay

Similar Issues Plugin performs a real-time background search on the JIRA to find out similar issues as soon as you start to write summary field of an issue. Found similar/duplicate issues are displayed below the summary field. It also highlights matching terms within the result list so that it is easier to see why two issues are similar. Similarity search is also performed in the summary and description of issues. Best matches are displayed on the top. In addition to summary of the issue, issue type and issue key are also displayed. If issue is resolved it’s key is displayed with strikethrough style.

Similar Issues Overlay

As you can see from the above screenshot, issue keys are a link to actual issues and you can open them directly in the new browser tab.

Similar Issues Tab

While working on an existing issue, we sometimes need quick access to similar issues and Similar Issues Plugin could also be a help here. Plugin adds a “Similar Issues” tab to issue’s tab list and when you click on it, issues similar to currently viewed issues are displayed. Similar issues list is not loaded until you open the relevant tab, so plugin does not cause any delay in loading the page.

Similar Issues Tab

Similar Issues Settings

Actually this plugin is an ‘install and forget’ type of plugin; you can start using it immediately after its installation without a single configuration. But if you need to tweak how the plugin works and how overlays are displayed, you can access plugin’s setting panel from plugin administration menu of JIRA.

Plugin Settings

Configuration Option Description
Similarity Mode There are two alternatives. Loose and Strict. Strict mode requires all search terms to exist in similar issues, so it returns much less result than Loose mode. Loose performs more loose similarity check. Loose mode is set as default.
Theme Currently there are two alternatives, light and dark. Light is the default and matches the color schema of JIRA. Similar results overlay takes more attention with the dark mode due to the contrast with JIRA’s look and feel. Light mode is set as default.
Display Mode There are two modes, overlay and inline. In overlay mode similar issues are displayed in a popup just below the summary field but on top of following fields. In inline mode, similar issues are displayed between summary and fields following it. All fields are pushed down to show similar issue list. When you finish editing summary fields similar issue list is hidden in both mode. Overlay mode is set as default.
Number of Issues to Display Default value is 5. This value could be between 3 and 10. It shows how many issues will be listed in the similar issues list.

If you have any problem while using the plugin, you can always enter a support request on or contact me on Atlassian Answers.

You can also download this manual as PDF.


VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)

Worklog PRO-A More Effective Way for Entering Worklogs in JIRA


Keeping track of time spent on anything is a requirement in a lot of organizations. Unfortunately most of the time this is a manual process and correctness of entered work logs are low. Worklog PRO is a JIRA plugin that aims to increase correctness of work logs by making entering work logs a lot easier. How this is possible?

Periodic Worklog

Periodic Work Logs

Sometimes our tasks spans more than one day. But JIRA’s build in work log mechanism requires you to enter work logs day by day. Worklog PRO allows you to enter a specific amount of time to all the days within a given range.

Periodic Worklog

In addition to allowing you to enter worklog for current issue, this dialog allows you to log work to any issue in JIRA. At top of the dialog a predefined list of filters is displayed that makes locating issues easier. Any keyword you have search in the issue box will be searched within the selected filter.

  • Recent: Shows latest issues you have viewed
  • No Worklog: Shows latest issues you have viewed but you haven’t logged any work yet
  • Assigned: Shows latest issues assigned to you
  • Reported: Shows latest issues you have reported
  • Watched: Shows latest issues you have added to you watch list
  • Voted: Shows latest issues you have voted
  • Filters: You can search a filter from you favorite or owned filters. Latest issues from this filter will be displayed also any keyword you have written in issue search box will be searched in that filter.

Worklog Timer

It is sometimes difficult to estimate how much time you have spent on an issue. Also in some type of issues you may need very accurate timing, for you are charging your customers according to time you spent. Worklog PRO includes a timer that is attach to bottom of JIRA’s screen. Just start it before starting to work on an issue and it will interactively count how much you have spent. When you stopped the counter it will display the work log entry screen.
One additional usage of this counter is motivation, seeing time passing will motivate you to work harder. As said, “You may be delayed, but time will not”.


Worklog by User Panel

A lot of people forget to enter work logs to issues, especially if they are not the one who is resolving the issue. Most of the time, in addition to person resolving the issue, a lot of people is involved during the lifecycle of an issue. Person reporting the issue or people involved in the discussion all spent time on the issue. Plugin makes it a lot easier to find out the issues you involved somehow, list the issues, search for a keyword. Even it could show you only the issues you have involved but not entered any work log yet.

Worklog by User


VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)

Maximum Heap Available to Dalvik in Different Android Devices

Although physical memory of Android devices are reached to 3GB nowadays, only a limited portion of this memory is available to an application. Amount of this memory may change with different version of the Android even for the same device model.

You can access row data from here


Device Model Heap Available To Dalvik Virtual Machine
HUAWEI P6-U06 268
HTC One 201
LG Nexus 4 201
Sony C6603 201
Sony C6903 201
Samsung GT-I9100 134 67 50
Samsung GT-I9500 134 100
Samsung GT-I9505 134
Samsung GT-N7000 134 67
LGE LG-F240K 134
Samsung SM-N9005 134
LGE LG-F200K 134
Samsung SM-N900 134
Samsung GT-I9100G 134 67 50
GENERAL_MOBILE Discovery 134
Samsung SCH-I545 134
Samsung SM-N9000Q 134
HUAWEI Y300-0100 134
Samsung SM-N900V 134
Samsung GT-I9295 134
Samsung SHW-M250K 134 50
Micromax A116 134 100
LGE LG-F240L 134
LGE LG-D802 134
Samsung SM-G900F 134
HUAWEI G525-U00 134
LGE LG-LS980 134
Prestigio PAP5044DUO 134
Samsung SM-N900S 134
Samsung SAMSUNG-SM-N900A 134
LGE LG-F180L 100
Samsung GT-I8190 100 67
Samsung SAMSUNG-SGH-I747 100 67
Samsung SGH-T999 100 67
Samsung SCH-I535 100 67
Samsung SGH-T999L 100 67
Samsung SPH-L710 100
ZTE N986 100
Alps S5E 100
JSR Andromax AD682J 100
Samsung SM-G7102 100
HTC Desire 601 100
Symphony W82 100
TCT Orange_infinity_996 100
LGE LG-LG870 100
Samsung GT-I9300 67
Samsung GT-N7100 67
Samsung GT-S7562 67
Samsung GT-I9070 67
Samsung GT-S5830i 67
Samsung GT-N8000 67
Samsung SGH-I727 67
Samsung GT-I9195 67
Samsung GT-N5100 67
Samsung GT-I9200 67
Samsung GT-I8190N 67
Samsung GT-N7105 67
Samsung GT-S7560 67
Samsung GT-I9152 67
Samsung GT-I9001 67
Samsung GT-I9100T 67 50
Samsung SM-T310 67
Samsung GT-I8160 67
Samsung GT-I9305 67
Samsung GT-I8530 67
Samsung GT-N8005 67
HUAWEI U8815 67
Sony Ericsson LT28h 67
Samsung SHV-E210L 67
Samsung GT-I8150 67
Samsung SGH-T989 67
Samsung SC-06D 67
Samsung GT-I8190L 67
Alps Symphony Xplorer W71 67
Samsung GT-N5105 67
LGE LG-E455 67
Samsung SC-02B 67
Sony C1905 67
Motorola DROID RAZR 67
Samsung GT-S5830i 67
Samsung GT-S5360 67
Lge LG-MS770 67
Samsung GT-I9082 58
Samsung GT-I9105 58
Samsung GT-I9105P 58
Samsung GT-I8262 50
Samsung GT-I8552 50
Samsung GT-S7582 50
Samsung GT-S7272 50
Samsung SGH-T599N 50
Karbonn Titanium S5 50
Samsung GT-S7580 50
Samsung GT-S6810 50
LGE LG-P705 50
Sony Ericsson LT18i 50 33
Samsung GT-S5282 50
Alps Celkon A900 41
Sony Ericsson SK17i 33
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)

Share Text Photo

New version of our app Share Text Photo is published. We have add some animations using the build in animation features of IOS. It is really easy to add some eye candy to an app in IOS.

For the ones who don’t know what Share Text photo is, it is an application for writing a text with custom styles and sharing that text as a photo on social networks like Twitter, Instagram and Facebook. Since it is shared as text, you could write more than 140 characters on twitter. New features of 1.2 version are:

-New backgrounds
-Ability to change text location with pan
-History of previously shared text photos
-Shutter animation to post
-Page view (like iBooks) and delete animations to history
-Ability to select from your own photos or from camera




VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)

Android Kargo Takip Uygulaması

Günümüzde bir çoğumuz Internet üzerinden alış veriş yapıyoruz. Özellikle yurt dışından yapılan alış verişlerde kargonun nerede olduğunu takip etmek zor oluyor. PTT’nin takip sayfası oldukca kullanışsız ve yurt dışından yapılan bir gönderinin PTT takip sayfasında çıkması biraz vakit alıyor. Bazı alış veriş siteleri de kargo takip numarasını mail ile göndermeyip kendi siteleri üzerinden hesabınıza girip kendi sağladıkları arayüz üzerinden bu bilgiyi veriyorlar. Ben de kargom nerede diye kontrol etmeyi kolaylaştıracak bir Android uygulaması geliştirdim. Bu uygulama Türkiye’de hizmet veren bütün kargo şirketlerini kapsadığı gibi, UPS, Fedex, DHL ve China Post (Çin’den gelen postalar/kargolar için) gibi uluslar arası gönderi yapan kargo şirketlerini destekliyor. Uygulamayı Android Market’den indirebilirsiniz, ismi “Kargo Takibi”.

Uygulama en son girdiğiniz takip numaralarını da saklıyor ve tekrar sorgulama yapmak için sadece listeden takip numarasını seçmeniz yeterli oluyor. Kargo şirketini kendisi tamamlıyor.

Uygulama siz takip numarasını yazdığınız zaman girdiğiniz formattan hangi kargo şirketine ait olduğunu çoğu zaman anlayabiliyor ve otomatik olarak şirket seçeneğini dolduruyor. Bu uygulamayı yaparken tabiki farklı kargo şirketlerinin farklı farklı takip numarası kullandıklarını farkettim ve bu formatları da sizler ile paylaşmak istedim. Uygulama dışında da işe yarar olduğunu düşünüyorum çünku takip bu numara fatura no vb. diğer bilgiler ile karıştırılabiliyor.

ARAS Kargo: Aras Kargo takip numarası 13 tane rakamdan oluşur. Örnek:4208993503499

China Post(Çin’den yapılan posta gönderileri için): China Post takip numarası R ile başlar ve CN ile biter. R’den sonra bir harf daha vardır ve 9 tane rakam içerir. Örnek:RA697576059CN

DHL: DHL takip numarası 10 tane rakamdan oluşur. Örnek:2217900993

Fedex: FEDEX takip numarası 12 tane rakamdan oluşur. Örnek:802416569979

MNG Kargo: MNG Kargo takip numarası iki adet harf ile başlar ve ardından genellikle 6 tane rakam gelir. Tamamen rakamlardan oluştuğu veya 2 harften sonra 4 rakam gelen takip numaraları da olabilir. Örnek:DB501983

PTT Kargo: PTT Kargo takip numarası genellikle 13 adet rakamdan oluşur. 2 adet harfin ardından 11 adet rakam gelecek şekilde de olabilir. Örnek:AP00869174550 veya 2789339611984

PTT Kargo Yurt Dışı: PTT Yurt Dışı takip numarası R ile başlar ardından 1 tane harf gelir ve bunu 9 adet rakam izler. İki adet harf ile biter. Bu harf gönderinin yapıldığı ülkeye göre değişir. Mesela Çin’den yapılan gönderilerin takip kodu CH ile biter. Örnek:RS915119275CH

Sürat Kargo: Sürat Kargo takip numarası 12 adet rakam ve harfden oluşur. Örnek:2aca211a3b5b

UPS Türkiye: UPS takip numarası H veya U ile başlar. Harf ve ramaklardan oluşur. Toplamda 16 karakter uzunluktadır. Örnek:U34B519G2533391

Yurtiçi Kargo: Yurtiçi Karg takip numarası 12 tane rakamdan oluşur. Örnek:608993503499

VN:F [1.9.22_1171]
Rating: 10.0/10 (2 votes cast)

Component Level Versioning and Bundle of Components in JIRA

Each project in JIRA has its own set of components and versions. Versions are defined at project level so any version is valid for any component of the project. For a very long time ability to use component specific version numbers within the JIRA is one of the most requested feature. There are various feature requests opened just for this feature, like JRA-3501. If your project contains components that have different version numbers you have two choices:

You may make your each component a different project

Advantage of this approach is you may have finer level of detail in managing the project. You may assign different issue schemas, workflows or assign different persons to different roles. Disadvantage is your project administration may become more complex. Also you have to define special filters to see all issues of higher level project.

You may use “Component and Bundle Versions for JIRA” plugin

This plugin allows you to assign different versions to different components within your JIRA project. This component specific version is enforced on every issue operation like create, edit, inline edit, workflow screens. Possibility of selecting incorrect component and version pair for an issue is greatly reduced. This plugin also allows you to group different version of different components into a bundle. Bundles has different versions than components. In any issue screen if no component is selected, plug-in only allows versions that are assigned to a bundle. You can also filter issues using two new JQL functions; affectsBundle and fixedInBundle. affectsBundle function takes a list of bundle names and returns all issues that are affecting the components in the bundle or directly entered for bundle without specifying any component. fixedInBundle JQL function works similar to affectsBundle but works for “fix version” field.
You may have more detailed explanation of plug-in at its home page and help pages. You can also visit the plug-in’s page at Atlassian Marketplace.

Use following links to take advantage of a limited time promotions:

Component and Bundle Versions for JIRA

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)

CMMI, Scrum, Kanban

I have just checked trend of 3 popular process. As you can see, CMMI goes down for a long time. The interesting part is CMMI is very popular in India, China, Pakistan, Taiwan then it is in the other parts of the world. On the other hand scrum is more popular in Europe.

Google Trends for Scrum, Kanban, CMMI

Google Trends for Scrum, Kanban, CMMI

Popularity of CMMI by Country

Popularity of CMMI by Country

Popularity of Scrum by Country

Popularity of Scrum by Country

VN:F [1.9.22_1171]
Rating: 8.7/10 (3 votes cast)